X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 846698B9EDC for ; Thu, 10 Feb 2005 05:30:30 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 90524-09 for ; Thu, 10 Feb 2005 05:29:14 +0000 (GMT) Received: from mammoth.utopiasystems.net (meridian1.utopiasystems.net [66.150.45.40]) by svr1.postgresql.org (Postfix) with ESMTP id 2708F8B9EC4 for ; Thu, 10 Feb 2005 05:29:12 +0000 (GMT) Received: from 67.173.111.107 ([67.173.111.107]) by mammoth.utopiasystems.net ([172.16.1.40]) via Exchange Front-End Server mail.utopiasystems.net ([172.16.1.42]) with Microsoft Exchange Server HTTP-DAV ; Thu, 10 Feb 2005 05:26:03 +0000 User-Agent: Microsoft-Entourage/11.1.0.040913 Date: Wed, 09 Feb 2005 23:28:44 -0600 Subject: Re: PG 7.4: duplicate rows in violation of unique From: Steve Lane To: Tom Lane Cc: "Joshua D. Drake" , , Jesse LaVere Message-ID: In-Reply-To: <22859.1108011047@sss.pgh.pa.us> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.544 tagged_above=0 required=5 tests=AWL, RCVD_NUMERIC_HELO X-Spam-Level: * X-Archive-Number: 200502/78 X-Sequence-Number: 16246 Tom: Thanks. What's odd here is that we seemed to have none of them, and then found a bunch, immediately after processes starting crashing. This is not the first time this has happened -- we had an outbreak once before. It's quite possible that we had these lurking in there for a while, and only found them during the checks we did after the process crashes. Does 7.4.6 incorporate the patch for this? -- sgl > From: Tom Lane > Date: Wed, 09 Feb 2005 23:50:47 -0500 > To: Steve Lane > Cc: "Joshua D. Drake" , , > Jesse LaVere > Subject: Re: [ADMIN] PG 7.4: duplicate rows in violation of unique > > Steve Lane writes: >> Sorry -- 7.4.5 > > I'm wondering if this could be related to this post-7.4.5 fix: > > 2004-10-13 18:22 tgl > > * contrib/pgstattuple/pgstattuple.c, > src/backend/access/heap/heapam.c, > src/backend/utils/adt/ri_triggers.c (REL7_4_STABLE): Repair > possible failure to update hint bits back to disk, per > http://archives.postgresql.org/pgsql-hackers/2004-10/msg00464.php. > > What you are describing sure sounds like a foulup in commit status > marking for multiple versions of a row. I'm not convinced it would be > fixed by the abovementioned patch, but it sounds close. > > regards, tom lane