| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Steve Lane <slane(at)soliantconsulting(dot)com> |
| Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-admin(at)postgresql(dot)org, Jesse LaVere <jlavere(at)soliantconsulting(dot)com> |
| Subject: | Re: PG 7.4: duplicate rows in violation of unique |
| Date: | 2005-02-10 04:50:47 |
| Message-ID: | 22859.1108011047@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Steve Lane <slane(at)soliantconsulting(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Lane | 2005-02-10 05:28:44 | Re: PG 7.4: duplicate rows in violation of unique |
| Previous Message | Steve Lane | 2005-02-10 01:46:29 | Re: PG 7.4: duplicate rows in violation of unique |