From: | yamt(at)mwd(dot)biglobe(dot)ne(dot)jp (YAMAMOTO Takashi) |
---|---|
To: | Kevin(dot)Grittner(at)wicourts(dot)gov |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: SSI bug? |
Date: | 2011-02-17 04:18:48 |
Message-ID: | 20110217041848.BF26E19CF3F@mail.netbsd.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2011-02-17 04:23:33 | Re: Debian readline/libedit breakage |
Previous Message | Robert Haas | 2011-02-17 04:16:26 | Re: WALInsertLock contention |