On Mon, 2019-12-09 at 11:41 -0800, John Hardin wrote: > This sounds more like the "does that tuple already exist?" logic is > failing, causing it to think it needs to create a new entry, which > the unique key is (correctly) preventing. > > You don't lightly bypass unique keys. They are there for a reason. > Fair enough. Since this is the first reference I remember seeing to using PostgreSQL with TxRef I assumed that Benny's cry for help was due to a difference in the way it handled duplicate keys compared with the database that normally supports it.
Martin
