[BUGS] Bug Report with Postgres 7.4 on AIX 5.3

2005-05-10 Thread Vincent Vanwynsberghe
Dear Support, We try to install Postgres 7.4 on AIX 5.3 (IBM,9111-520). The compilation is good and we are able to start the postmaster. When we try to start the psql we got the following error : FATAL: unsupported frontend protocol 0.0: server supports 1.0 to 3.0 We run the psql under the AIX d

[BUGS] BUG #1656: ResultSetMetaData.getColumnDisplaySize() returns value -1

2005-05-10 Thread Sergio Lob
The following bug has been logged online: Bug reference: 1656 Logged by: Sergio Lob Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.1 Operating system: Linux edared30 2.4.21-27.0.4.ELsmp #1 SMP Sat Apr 16 18:43:06 EDT 2005 i686 i686 Description:ResultSetMetaD

Re: [BUGS] Bug Report with Postgres 7.4 on AIX 5.3

2005-05-10 Thread Tom Lane
Vincent Vanwynsberghe <[EMAIL PROTECTED]> writes: > In our platform the sizeof of struct sockaddr_un is 1025 and the sizeof of > SockAddr is 144. Doesn't AIX provide struct sockaddr_storage? That struct has to be at least as large as any of the other platform-specific sockaddr structs.

Re: [BUGS] BUG #1656: ResultSetMetaData.getColumnDisplaySize()

2005-05-10 Thread Kris Jurka
On Tue, 10 May 2005, Sergio Lob wrote: > Bug reference: 1656 > PostgreSQL version: 8.0.1 > Description:ResultSetMetaData.getColumnDisplaySize() returns value > -1 > Details: > > ResultSetMetaData.getColumnDisplaySize() returns value -1 for several > columns of answer set generated

Re: [BUGS] BUG #1578: ::bit(n) behaves "differently" if applied to bit

2005-05-10 Thread Bruce Momjian
Celia McInnis wrote: > > The following bug has been logged online: > > Bug reference: 1578 > Logged by: Celia McInnis > Email address: [EMAIL PROTECTED] > PostgreSQL version: 8.0.1 > Operating system: Linux > Description:::bit(n) behaves "differently" if applied to bi

Re: [BUGS] BUG #1578: ::bit(n) behaves "differently" if applied to bit

2005-05-10 Thread Tom Lane
Bruce Momjian writes: > ... Though this is slightly inconsistent in how it works with a > bit string, it does seem the most useful approach. Also, this is a behavior that we changed in 8.0 in response to previous complaints. Before changing it again, I'd want to see a pretty detailed analysis of