Re: Change COPY ... ON_ERROR ignore to ON_ERROR ignore_row

Jim Jones <jim.jones@uni-muenster.de>

From: Jim Jones <jim.jones@uni-muenster.de>

To: "David G. Johnston" <david.g.johnston@gmail.com>

Cc: jian he <jian.universality@gmail.com>, Yugo NAGATA <nagata@sraoss.co.jp>, torikoshia <torikoshia@oss.nttdata.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2024-02-16T23:05:18Z

Lists: pgsql-hackers

On 16.02.24 21:31, David G. Johnston wrote:
> Yes.  In particular not all columns in the table need be specified in
> the copy command so while the parsed input data is all nulls the
> record itself may not be.

Yeah, you have a point there.
I guess if users want to avoid it to happen they can rely on NOT NULL
constraints.

Thanks

-- 
Jim

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

file_fdw: Add regression test for file_fdw with ON_ERROR='set_null'
- d8879d34b9dd 19 (unreleased) landed
Add COPY (on_error set_null) option
- 2a525cc97e19 19 (unreleased) landed
Add REJECT_LIMIT option to the COPY command.
- 4ac2a9beceb1 18.0 cited
Add log_verbosity = 'silent' support to COPY command.
- e7834a1a251d 18.0 cited
Add new COPY option LOG_VERBOSITY.
- f5a227895e17 17.0 cited