| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| 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>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 03:54:20 |
| Message-ID: | 145C6023-32A1-483A-9279-9D030DCD38B7@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On Mar 2, 2025, at 19:44, me nefcanto <sn(dot)1361(at)gmail(dot)com> wrote:
>
> As I have specified in the bug thread, from 11 RDBMSs, 7 support this. Thus it's not an uncommon weird request.
If your organization is interested in producing a design and a patch, or paying a developer or organization to do so, that would be the best way forward. Everyone who works on the core PostgreSQL code is either a volunteer or extremely busy. Those that are paid to work on PostgreSQL usually have their priorities mapped out for months (years?) already. The best way to convince the community to adopt a feature to come bearing a high-quality patch. That's no guarantee, of course, but the probability is much higher that way.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-03-03 04:07:27 | Re: Please implement a catch-all error handler per row, for COPY |
| Previous Message | me nefcanto | 2025-03-03 03:44:52 | Re: Please implement a catch-all error handler per row, for COPY |