Changing just the one appears to resolve the oid bug. Should probably talk
to neilc to see why he changed it.
I will pass along a patch for this particular case to -patches shortly
----- Original Message -----
From: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
Sent: Wednesday, July 27, 2005 11:57 AM
Subject: Re: [HACKERS] RESULT_OID Bug
> Andrew - Supernews wrote:
>>On 2005-07-27, Michael Fuhr <mike(at)fuhr(dot)org> wrote:
>>>So far the problem does seem to be specific to whatever PL/pgSQL's
>>>is doing, and it affects ROW_COUNT as well as RESULT_OID. I haven't
>>>been able to reproduce the problem with PL/Tcl or with C and SPI.
>>src/pl/plpgsql/src/pl_exec.c, function exec_stmt_getdiag, uninitialized
> nice catch. I see the "= false" removed in about 5 places in this change:
> Is this the only one that matters?
> (another) andrew
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
In response to
pgsql-hackers by date
|Next:||From: Alvaro Herrera||Date: 2005-07-27 20:24:31|
|Subject: Re: Integrated autovacuum|
|Previous:||From: Kevin McArthur||Date: 2005-07-27 20:15:23|
|Subject: Re: RESULT_OID Bug|