Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tp1QY-00H9vO-Ie for pgsql-general@arkaria.postgresql.org; Mon, 03 Mar 2025 08:45:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1towuL-00DkhF-7X for pgsql-general@arkaria.postgresql.org; Mon, 03 Mar 2025 03:55:57 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1towuK-00DkgS-SJ for pgsql-general@lists.postgresql.org; Mon, 03 Mar 2025 03:55:56 +0000 Received: from smtp73.ord1d.emailsrvr.com ([184.106.54.73]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1towuH-000dG5-06 for pgsql-general@lists.postgresql.org; Mon, 03 Mar 2025 03:55:56 +0000 X-Auth-ID: xof@thebuild.com Received: by smtp10.relay.ord1d.emailsrvr.com (Authenticated sender: xof-AT-thebuild.com) with ESMTPSA id 831BAA01A4; Sun, 2 Mar 2025 22:54:51 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.1\)) Subject: Re: Please implement a catch-all error handler per row, for COPY From: Christophe Pettus In-Reply-To: Date: Sun, 2 Mar 2025 19:54:20 -0800 Cc: Greg Sabino Mullane , "David G. Johnston" , Tom Lane , pgsql-general@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: <145C6023-32A1-483A-9279-9D030DCD38B7@thebuild.com> References: <2961422.1740846012@sss.pgh.pa.us> To: me nefcanto X-Mailer: Apple Mail (2.3776.700.51.11.1) X-Classification-ID: 0dc5e405-e6ed-4716-ae02-f6c4cf8fe6e1-1-1 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On Mar 2, 2025, at 19:44, me nefcanto wrote: >=20 > 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.=