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 2768C8B9F71 for ; Thu, 10 Feb 2005 04:51:04 +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 75237-09 for ; Thu, 10 Feb 2005 04:50:48 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id BE94F8B9F1F for ; Thu, 10 Feb 2005 04:50:48 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j1A4olQJ022860; Wed, 9 Feb 2005 23:50:47 -0500 (EST) To: Steve Lane Cc: "Joshua D. Drake" , pgsql-admin@postgresql.org, Jesse LaVere Subject: Re: PG 7.4: duplicate rows in violation of unique In-reply-to: References: Comments: In-reply-to Steve Lane message dated "Wed, 09 Feb 2005 19:46:29 -0600" Date: Wed, 09 Feb 2005 23:50:47 -0500 Message-ID: <22859.1108011047@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200502/77 X-Sequence-Number: 16245 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