| commit | d59383924c580a77a2346d9b1284c8589b3d43e2 | |
| author | Tom Lane <tgl@sss.pgh.pa.us> | |
| Thu, 4 Aug 2022 18:16:26 +0000 (4 14:16 -0400) | ||
| committer | Tom Lane <tgl@sss.pgh.pa.us> | |
| Thu, 4 Aug 2022 18:16:26 +0000 (4 14:16 -0400) | ||
| tree | 7965108058271c8b7a912715d13bc9b6ea052569 | treesnapshot (tar.gz zip) |
| parent | 6ad86feecb246f6b9d1f097e2bf777775b7c2434 | commitdiff |
Fix check_exclusion_or_unique_constraint for UNIQUE NULLS NOT DISTINCT.
Adjusting this function was overlooked in commit 94aa7cc5f. The only
visible symptom (so far) is that INSERT ... ON CONFLICT could go into
an endless loop when inserting a null that has a conflict.
Richard Guo and Tom Lane, per bug #17558 from Andrew Kesper
Discussion: https://postgr.es/m/17558-3f6599ffcf52fd4a@postgresql.org
Adjusting this function was overlooked in commit 94aa7cc5f. The only
visible symptom (so far) is that INSERT ... ON CONFLICT could go into
an endless loop when inserting a null that has a conflict.
Richard Guo and Tom Lane, per bug #17558 from Andrew Kesper
Discussion: https://postgr.es/m/17558-3f6599ffcf52fd4a@postgresql.org
| src/backend/executor/execIndexing.c | diffblobblamehistory | |
| src/test/regress/expected/constraints.out | diffblobblamehistory | |
| src/test/regress/sql/constraints.sql | diffblobblamehistory |