Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 053741337990 for ; Sun, 13 Feb 2011 23:08:34 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 33401-02 for ; Mon, 14 Feb 2011 03:08:28 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11]) by mail.postgresql.org (Postfix) with ESMTP id B6E96133740B for ; Sun, 13 Feb 2011 23:08:26 -0400 (AST) Received: by mail.netbsd.org (Postfix, from userid 1270) id B545C19D6D7; Mon, 14 Feb 2011 03:08:24 +0000 (UTC) To: Kevin.Grittner@wicourts.gov Cc: pgsql-hackers@postgresql.org Subject: Re: SSI bug? In-Reply-To: Your message of "Sat, 12 Feb 2011 11:53:57 -0600" <4D5674D5020000250003A911@gw.wicourts.gov> References: <4D5674D5020000250003A911@gw.wicourts.gov> X-Mailer: Cue version 0.8 (100217-1432/takashi) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Message-Id: <20110214030824.B545C19D6D7@mail.netbsd.org> Date: Mon, 14 Feb 2011 03:08:24 +0000 (UTC) From: yamt@mwd.biglobe.ne.jp (YAMAMOTO Takashi) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-4.2 tagged_above=-5 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3 X-Spam-Level: X-Archive-Number: 201102/1230 X-Sequence-Number: 182019 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