I uploaded a patch for postgresql on https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7218 a while ago - but I haven't had time to clean it up into something that should be included into a release.
It might serve as inspiration for someone else before I end up having time to get to it, though. > On Dec 9, 2019, at 4:00 PM, Martin Gregorie <[email protected]> wrote: > > 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 > -- Daniel J. Luke
