Re: RESULT_OID Bug

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
Subject: Re: RESULT_OID Bug
Date: 2005-07-27 22:35:02
Message-ID: 20050727223502.GA26777@winnie.fuhr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Larry Rosenman 2005-07-27 22:38:46 Sanity Check?
Previous Message Simon Riggs 2005-07-27 22:18:10 Re: Checkpoint cost, looks like it is WAL/CRC