Incrementing comand counter is not enough - dirty reads are required
to handle concurrent PK updates.
What's that with you and dirty reads? Every so often you tell
me that something would require them - you really like to
read dirty things - no? :-)
Dirty things occure -
update a set a=a+1 where a2;
ERROR: Cannot insert a duplicate key into unique index a_pkey
We use uniq index for UK/PK but shouldn't. Jan?
What else can you use than an index? A deferred until
statement end trigger checking for duplicates? Think it'd
have a
