Hiroshi Inoue <[EMAIL PROTECTED]> writes:
> What I meant is e.g.
> update t set .. = .. where ...;
> PostgreSQL ignores the tuples which don't satisfy the
> where clause at the point when the query started(or
> when the transaction started in serializable mode)
> even though it happend to look already update/delete
> (/insert)ed tuples.
Sure, but what we were discussing was the "duplicate key" error issued
by nbtinsert.c. AFAICS that depends on latest-commit status, not on
snapshots. Perhaps that behavior is itself a bug? If so, how would
you change it?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
