Sounds plausible.
Can anyone comment on whether the other instances of isnull=false being
removed need to be reset to =false
Kevin McArthur
----- Original Message -----
From: "Michael Fuhr" <mike@fuhr.org>
To: "Kevin McArthur" <postgresql-list@stormtide.ca>
Cc: "Andrew Dunstan" <andrew@dunslane.net>; <andrew@supernews.com>;
<pgsql-hackers@postgresql.org>
Sent: Wednesday, July 27, 2005 3:35 PM
Subject: Re: [HACKERS] RESULT_OID Bug
> On Wed, Jul 27, 2005 at 01:20:29PM -0700, Kevin McArthur wrote:
>> Changing just the one appears to resolve the oid bug. Should probably
>> talk
>> to neilc to see why he changed it.
>
> Initializing isnull to false in exec_stmt_getdiag() appears to fix
> the bug on my Solaris 9 box as well. I'd guess the variations in
> behavior were due to different platforms having different garbage
> on the stack.
>
> --
> Michael Fuhr
> http://www.fuhr.org/~mfuhr/
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>
