| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | me nefcanto <sn(dot)1361(at)gmail(dot)com> |
| Cc: | Greg Sabino Mullane <htamfids(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Please implement a catch-all error handler per row, for COPY |
| Date: | 2025-03-03 04:07:27 |
| Message-ID: | 3558969.1740974847@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
me nefcanto <sn(dot)1361(at)gmail(dot)com> writes:
> The point is, that there is already an `on_error ignore` clause there. This
> means that somewhere there is a try/catch per row. If I'm wrong, please let
> me know.
You are wrong. See
https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=d9f7f5d32
https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=9e2d87011
and a ton of related commits.
It's possible that the specific case of unique-index violations
could be handled in a similar style. But "catch any error whatever"
is simply not going to happen here, because a subtransaction per
row is not practical.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2025-03-03 05:33:07 | Re: Please implement a catch-all error handler per row, for COPY |
| Previous Message | Christophe Pettus | 2025-03-03 03:54:20 | Re: Please implement a catch-all error handler per row, for COPY |