Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 498E19FB37B for ; Mon, 29 Jan 2007 14:42:51 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 12103-04 for ; Mon, 29 Jan 2007 14:42:44 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from fafnir.androme.com (fafnir.androme.com [62.58.96.158]) by postgresql.org (Postfix) with ESMTP id DB9AF9FA320 for ; Mon, 29 Jan 2007 14:42:45 -0400 (AST) Received: by fafnir.androme.com (Postfix, from userid 1003) id 53EE5B99A9A; Mon, 29 Jan 2007 19:42:44 +0100 (CET) Message-ID: <45BE4024.8010506@andromeiberica.com> Date: Mon, 29 Jan 2007 19:42:44 +0100 From: Arnau Reply-To: arnaulist@andromeiberica.com User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: "pgsql-admin@postgresql.org" Subject: Re: Very strange postgresql behaviour References: <45BDE670.8010607@andromeiberica.com> <10668.1170084953@sss.pgh.pa.us> In-Reply-To: <10668.1170084953@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/264 X-Sequence-Number: 24420 Tom Lane wrote: > Arnau writes: >> I have postgresql 7.4.2 running on debian and I have the oddest >> postgresql behaviour I've ever seen. > > Is this specific to these two rows? If so it might be a case of this > bug, which was repaired in 7.4.13: I don't know, we have discovered those two rows but I'm not sure if there are more. Is there any way to check it? > > http://archives.postgresql.org/pgsql-general/2006-05/msg00756.php > http://archives.postgresql.org/pgsql-committers/2006-05/msg00174.php > > 2006-05-19 12:31 tgl > > * src/backend/executor/nodeIndexscan.c (REL7_4_STABLE): Fix nasty > bug in nodeIndexscan.c's detection of duplicate tuples during a > multiple (OR'ed) indexscan. It was checking for duplicate > tuple->t_data->t_ctid, when what it should be checking is > tuple->t_self. The trouble situation occurs when a live tuple has > t_ctid not pointing to itself, which can happen if an attempted > UPDATE was rolled back. After a VACUUM, an unrelated tuple could > be installed where the failed update tuple was, leading to one live > tuple's t_ctid pointing to an unrelated tuple. If one of these > tuples is fetched by an earlier OR'ed indexscan and the other by a > later indexscan, nodeIndexscan.c would incorrectly ignore the > second tuple. The bug exists in all 7.4.* and 8.0.* versions, but > not in earlier or later branches because this code was only used in > those releases. Per trouble report from Rafael Martinez Guerrero. > > REINDEX wouldn't fix this, although a table dump and reload would. > > regards, tom lane > > PS: please don't spam multiple lists with the same question. My intention was not spam mulitple lists, the problem was that I was not sure where to post this question. -- Arnau