Change COPY ... ON_ERROR ignore to ON_ERROR ignore_row

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Change COPY ... ON_ERROR ignore to ON_ERROR ignore_row
Date: 2024-01-26 15:08:29
Message-ID: CAKFQuwawy1e6YR4S=j+y7pXqg_Dw1WBVrgvf=BP3d1_aSfe_+Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

The option choice of "ignore" in the COPY ON_ERROR clause seems overly
generic. There would seem to be two relevant ways to ignore bad column
input data - drop the entire row or just set the column value to null. I
can see us wanting to provide the set to null option and in any case having
the option name be explicit that it ignores the row seems like a good idea.

David J.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2024-01-26 15:09:04 Re: POC: GROUP BY optimization
Previous Message David G. Johnston 2024-01-26 15:04:45 Re: Small fix on COPY ON_ERROR document