From: yamt@mwd.biglobe.ne.jp
To: Kevin.Grittner@wicourts.gov
Cc: pgsql-hackers@postgresql.org
Subject: Re: SSI bug?
Date: Mon, 14 Feb 2011 03:08:24 +0000 (UTC)
Message-ID: <20110214030824.B545C19D6D7@mail.netbsd.org> (raw)
In-Reply-To: <4D5674D5020000250003A911@gw.wicourts.gov>
References: <4D5674D5020000250003A911@gw.wicourts.gov>
hi,
> I wrote:
>
>> it seems likely that such a cycle might be related to this new
>> code not properly allowing for some aspect of tuple cleanup.
>
> I found a couple places where cleanup could let these fall through
> the cracks long enough to get stale and still be around when a tuple
> ID is re-used, causing problems. Please try the attached patch and
> see if it fixes the problem for you.
>
> If it does, then there's no need to try to track the other things I
> was asking about.
thanks. unfortunately the problem still happens with the patch.
YAMAMOTO Takashi
>
> Thanks!
>
> -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: <20110214030824.B545C19D6D7@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