From: yamt@mwd.biglobe.ne.jp
To: Kevin.Grittner@wicourts.gov
Cc: pgsql-hackers@postgresql.org
Subject: Re: SSI bug?
Date: Thu, 17 Feb 2011 04:18:48 +0000 (UTC)
Message-ID: <20110217041848.BF26E19CF3F@mail.netbsd.org> (raw)
In-Reply-To: <4D5C46BB020000250003AB40@gw.wicourts.gov>
References: <4D5C46BB020000250003AB40@gw.wicourts.gov>
hi,
> YAMAMOTO Takashi wrote:
>
>> might be unrelated to the loop problem, but...
>
> Aha! I think it *is* related. There were several places where data
> was uninitialized here; mostly because Dan was working on this piece
> while I was working on separate issues which added the new fields.
> I missed the interaction on integrating the two efforts. :-(
> The uninitialized fields could lead to all the symptoms you saw.
> I've reviewed, looking for other similar issues and didn't find any.
>
> Could you try the attached patch and see if this fixes the issues
> you've seen?
with your previous patch or not?
YAMAMOTO Takashi
>
> -Kevin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: yamt@mwd.biglobe.ne.jp, Kevin.Grittner@wicourts.gov
Subject: Re: SSI bug?
In-Reply-To: <20110217041848.BF26E19CF3F@mail.netbsd.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox