Re: [BUGS] Column Name parameter problem

2005-09-28 Thread Tomas Zerolo
On Wed, Sep 28, 2005 at 12:25:54PM -0700, vishal saberwal wrote: > hi, > > I am trying to create a stored procedure that takes a column name as > parameter and then uses it to sort the table for result set. > > create or replace function ptest_Sort_Select(varchar) returns setof ptest1 > as $$ > D

Re: [BUGS] BUG #1916: selection criteria from one outer join on clause applied to other joins

2005-09-28 Thread Tom Lane
"Kevin Grittner" <[EMAIL PROTECTED]> writes: > Description:selection criteria from one outer join on clause applied > to other joins I've committed a fix for this. Many thanks for the test case. regards, tom lane ---(end of broadcast)-

Re: [BUGS] Column Name parameter problem

2005-09-28 Thread David Fetter
On Wed, Sep 28, 2005 at 12:25:54PM -0700, vishal saberwal wrote: > hi, > > I am trying to create a stored procedure that takes a column name as > parameter and then uses it to sort the table for result set. You can't currently do this in PL/PgSQL. I believe this is scheduled for a fix in 8.2, bu

[BUGS] Column Name parameter problem

2005-09-28 Thread vishal saberwal
hi, I am trying to create a stored procedure that takes a column name as parameter and then uses it to sort the table for result set. create or replace function ptest_Sort_Select(varchar) returns setof ptest1 as $$ DECLARE     res ptest1%ROWTYPE; BEGIN     for res in         select * from ptest

Re: [BUGS] BUG #1916: selection criteria from one outer join on clause applied to other joins

2005-09-28 Thread Tom Lane
"Kevin Grittner" <[EMAIL PROTECTED]> writes: > Any idea on when a fix might be available, or what > conditions must exist in a query for this failure to occur? It would be fairly easy to fix just by disabling all consideration of deducing anything from outer-join conditions. I want to think a lit

Re: [BUGS] BUG #1916: selection criteria from one outer join

2005-09-28 Thread Kevin Grittner
I agree that it looks like "overenthusiastic propagation of implied equalities." (Nicely put.) I haven't tested whether this fails in any other version (we've moved all our instances to 8.1beta2 to pound it the best we can), but I see that Klint Gore has reported the test case fails in 7.4.7 and

Re: [BUGS] BUG #1915: ERROR: RETURN cannot have a parameter in function returning void at or near "NULL" at character 148

2005-09-28 Thread Tom Lane
"Roy Wood" <[EMAIL PROTECTED]> writes: > Description:ERROR: RETURN cannot have a parameter in function > returning void at or near "NULL" at character 148 > Obtained this error creating a Function which contained 'RETURN NULL;' on > the new 8.1-beta2 The complaint seems valid to me...

Re: [BUGS] Postgresql problem in AIX 5.3

2005-09-28 Thread Tom Lane
"Kelvin Lau" <[EMAIL PROTECTED]> writes: > createdb: could not connect to database template1: FATAL: unsupported > frontend protocol 0.0: server supports 1.0 to 3.0 This is a known problem caused by a bug in the system header files that IBM supplies. There may by now be an update available from

Re: [BUGS] BUG #1917: autovaccuum crashes

2005-09-28 Thread Alvaro Herrera
I wrote > On Wed, Sep 28, 2005 at 04:21:16AM +0100, Theo Schlossnagle wrote: > > > Doing large data loads via the COPY command into a set of schema-identical > > tables table1, table2, table3 all of which inherrit table. (simulating > > Oracle's partitioning). Periodically, we get: > > > > > >

Re: [BUGS] BUG #1917: autovaccuum crashes

2005-09-28 Thread Alvaro Herrera
On Wed, Sep 28, 2005 at 04:21:16AM +0100, Theo Schlossnagle wrote: > Doing large data loads via the COPY command into a set of schema-identical > tables table1, table2, table3 all of which inherrit table. (simulating > Oracle's partitioning). Periodically, we get: > > > LOG: autovacuum process

[BUGS] Postgresql problem in AIX 5.3

2005-09-28 Thread Kelvin Lau
Dear Sir/Madam, I have a question regarding Postgresql on AIX 5.3's compatibility, since there are reported problems for this combination in newsgroup. I have also tried to install it also. The installation was successful and there was a message indicating that. However, when I ran the command

[BUGS] BUG #1917: autovaccuum crashes

2005-09-28 Thread Theo Schlossnagle
The following bug has been logged online: Bug reference: 1917 Logged by: Theo Schlossnagle Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1devel Operating system: CentOS 4.1 (Linux 2.6.12.3) Description:autovaccuum crashes Details: We're running an otherwise

[BUGS] BUG #1915: ERROR: RETURN cannot have a parameter in function returning void at or near "NULL" at character 148

2005-09-28 Thread Roy Wood
The following bug has been logged online: Bug reference: 1915 Logged by: Roy Wood Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1-beta2 Operating system: Win32 Description:ERROR: RETURN cannot have a parameter in function returning void at or near "NULL" at

[BUGS] BUG #1918: Wireless Zero Configuration

2005-09-28 Thread Hector Arocho
The following bug has been logged online: Bug reference: 1918 Logged by: Hector Arocho Email address: [EMAIL PROTECTED] PostgreSQL version: 8.03 Operating system: Windows XP SP2 Description:Wireless Zero Configuration Details: I have an Intel wireless card on a Dell

Re: [BUGS] Can not build libpq.dll with BCC

2005-09-28 Thread CN
Thank you! Magnus, > This sounds like you need a newer Platform SDK. This define should be in > winsock2.h, per > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winsock > /winsock/windows_sockets_error_codes_2.asp. Probably your includes from > BCC are too old and needs updating.