Re: [BUG?] check_exclusion_or_unique_constraint false negative

Michail Nikolaev <michail.nikolaev@gmail.com>

From: Michail Nikolaev <michail.nikolaev@gmail.com>
To: "Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>
Cc: Amit Kapila <amit.kapila16@gmail.com>, "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Andres Freund <andres@anarazel.de>
Date: 2025-02-11T23:39:09Z
Lists: pgsql-hackers
Hello!

I realize proposed solution does not guarantee absent of false negative
cases...
It happens because I am looking just at XID values, but them have nothing
with transaction commitment order in the common case.

I'll look for some other option.

Best regards,
Mikhail.

Commits

  1. Add support for INSERT ... ON CONFLICT DO NOTHING/UPDATE.