From: | "Kevin McArthur" <postgresql-list(at)stormtide(dot)ca> |
---|---|
To: | "Michael Fuhr" <mike(at)fuhr(dot)org> |
Cc: | "Andrew Dunstan" <andrew(at)dunslane(dot)net>, <andrew(at)supernews(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: RESULT_OID Bug |
Date: | 2005-07-27 22:58:13 |
Message-ID: | 005401c592fe$ab3d7fd0$0701a8c0@kdesktop |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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(at)fuhr(dot)org>
To: "Kevin McArthur" <postgresql-list(at)stormtide(dot)ca>
Cc: "Andrew Dunstan" <andrew(at)dunslane(dot)net>; <andrew(at)supernews(dot)com>;
<pgsql-hackers(at)postgresql(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2005-07-27 23:09:58 | Re: VACUUM DATABASE |
Previous Message | Tom Lane | 2005-07-27 22:52:08 | Re: Sanity Check? |