Re: pg primary key bug?

pginfo <pginfo@t1.unisoftbg.com> writes:
> sorry, but we have the case number 3 in with the same problem.
> Also this time we do not find any linux box crash nor pg stop or restart.

Hmm, well there's *something* mighty curious about the history of this
table.  The xmin values span a range of almost 400,000 transactions and
yet the oids are twenty-three consecutive values.  Is this the only
table you've inserted into during the last 400K transactions?

It's also odd that there's so much empty space (only 37 rows in 60
pages).  It's hard to see how that could be unless there were many
updates on the table, but judging from the name and contents of the
table I can hardly see a reason for lots of updates.  How is this table
used exactly?  Do you do UPDATEs on it?  DELETEs?  SELECT FOR UPDATE?
Do you do VACUUM, or VACUUM FULL, or both?
        regards, tom lane