From: Tom Lane <tgl@sss.pgh.pa.us>
To: me nefcanto <sn.1361@gmail.com>
cc: pgsql-general@lists.postgresql.org
Subject: Re: Please implement a catch-all error handler per row, for COPY
In-reply-to: <CAEHBEOCqqkSitU5gx=8aHD3ZeLtRy-1eC=Xs=xB-thFNR9JpYA@mail.gmail.com>
References: <CAEHBEOCqqkSitU5gx=8aHD3ZeLtRy-1eC=Xs=xB-thFNR9JpYA@mail.gmail.com>
Comments: In-reply-to me nefcanto <sn.1361@gmail.com>
	message dated "Sat, 01 Mar 2025 18:48:41 +0330"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2961421.1740846012.1@sss.pgh.pa.us>
Date: Sat, 01 Mar 2025 11:20:12 -0500
Message-ID: <2961422.1740846012@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/2961422.1740846012%40sss.pgh.pa.us>
Precedence: bulk

me nefcanto <sn.1361@gmail.com> writes:
> Can you please provide a row-level catch-all handler for the copy command?

Very unlikely to happen.  COPY is not intended as a general purpose
ETL mechanism, and we don't want to load it down with features that
would create substantial performance penalties.  Which that would.

Even ignoring the performance angle, this request seems remarkably
ill-specified.  What is a "row-level handler" for errors that have
to do with identifying row boundaries?

			regards, tom lane