From: Tom Lane <tgl@sss.pgh.pa.us>
To: Steve Lane <slane@soliantconsulting.com>
Cc: Joshua D. Drake <jd@commandprompt.com>
Cc: pgsql-admin@postgresql.org, Jesse LaVere <jlavere@soliantconsulting.com>
Subject: Re: PG 7.4: duplicate rows in violation of unique
Date: Wed, 09 Feb 2005 23:50:47 -0500
Message-ID: <22859.1108011047@sss.pgh.pa.us> (raw)
In-Reply-To: <BE301915.12B5B%slane@soliantconsulting.com>
References: <BE301915.12B5B%slane@soliantconsulting.com>
Steve Lane <slane@soliantconsulting.com> 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
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, slane@soliantconsulting.com, jd@commandprompt.com, jlavere@soliantconsulting.com
Subject: Re: PG 7.4: duplicate rows in violation of unique
In-Reply-To: <22859.1108011047@sss.pgh.pa.us>
References: <BE301915.12B5B%slane@soliantconsulting.com> <22859.1108011047@sss.pgh.pa.us>
* 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