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 <[EMAIL PROTECTED]> > Date: Wed, 09 Feb 2005 23:50:47 -0500 > To: Steve Lane <[EMAIL PROTECTED]> > Cc: "Joshua D. Drake" <[EMAIL PROTECTED]>, <pgsql-admin@postgresql.org>, > Jesse LaVere <[EMAIL PROTECTED]> > Subject: Re: [ADMIN] PG 7.4: duplicate rows in violation of unique > > Steve Lane <[EMAIL PROTECTED]> 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 ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
