Glen Eustace <geustace@godzone.net.nz> writes:
> The table had 4 rows, all with the same OID. ( It is only supposed to have 1
> !!)
The existence of multiple rows with the same OID is not in itself a bug,
unless you have a unique index on OID on that table.
Jan evidently thinks that you have gotten into this state because a few
UPDATEs failed to invalidate the old copy of the row. That's one
possible scenario but it's somewhat difficult to credit. I'm wondering
about VACUUM dropping the ball while moving the row across page
boundaries, myself.
Can you provide:
1. samples of all the query sequences that update this table. (I'm
particularly interested in whether you use SELECT FOR UPDATE.)
2. A dump of the table including all system columns (ctid, oid, xmin,
cmin, xmax, cmax) as well as the user data. Also, what's the exact
schema declaration of the table? Are there any rules, triggers, foreign
key constraints attached to it?
Also, have you suffered any system crashes that might have interrupted
updates of this table?
regards, tom lane
