| From: | Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: COPY ON_CONFLICT TABLE; save duplicated record to another table. |
| Date: | 2026-05-15 11:56:46 |
| Message-ID: | CAN4CZFNe6CAB+F=L9ajNnKgjSMAiDN6XZNN4gazu=2NiEokQWg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I also noticed the early relation close mentioned by Jim, which can
crash the patch.
+ This uses the same mechanism as <link
linkend="sql-on-conflict"><command>INSERT ... ON
CONFLICT</command></link>.
+ However, exclusion constraints are not supported; only
<literal>NOT DEFERRABLE</literal>
+ unique constraints are checked for violations.
EXCLUDE USING gist (... WITH =, ... WITH &&) seems to work fine?
Except that the message mentions unique constraint violation.
I also checked the same trigger behaviors as in the other thread[1],
especially before triggers on the conflict table, and this patch
behaves similarly, it silently drops rows.
I think this could also use some more visibility/documentation about that.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vlad Lesin | 2026-05-15 12:29:30 | Re: [PATCH] Fix ProcKill lock-group vs procLatch recycle race |
| Previous Message | Nitin Motiani | 2026-05-15 11:53:31 | Re: [PATCH] Fix for bug #19474: LIKE fails to match literal backslashes with nondeterministic collations |