Re: Change COPY ... ON_ERROR ignore to ON_ERROR ignore_row - Mailing list pgsql-hackers

From Jim Jones
Subject Re: Change COPY ... ON_ERROR ignore to ON_ERROR ignore_row
Date
Msg-id 6eac5b45-7f45-4c7a-aae1-e90db8be2e08@uni-muenster.de
Whole thread Raw
In response to Re: Change COPY ... ON_ERROR ignore to ON_ERROR ignore_row  ("David G. Johnston" <david.g.johnston@gmail.com>)
List 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




pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: Add bump memory context type and use it for tuplesorts
Next
From: Tom Lane
Date:
Subject: Re: Add bump memory context type and use it for tuplesorts