Horton
Menu

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

Yi Ding <dingyi_yale@163.com>

View thread
From: "Yi Ding" <dingyi_yale@163.com>
To: "Fujii Masao" <masao.fujii@gmail.com>
Cc: "Peter Eisentraut" <peter@eisentraut.org>, "jian he" <jian.universality@gmail.com>, "Matheus Alcantara" <matheusssilv97@gmail.com>, torikoshia <torikoshia@oss.nttdata.com>, "Masahiko Sawada" <sawada.mshk@gmail.com>, "vignesh C" <vignesh21@gmail.com>, "Jim Jones" <jim.jones@uni-muenster.de>, "Kirill Reshke" <reshkekirill@gmail.com>, "Fujii Masao" <masao.fujii@oss.nttdata.com>, "David G. Johnston" <david.g.johnston@gmail.com>, "Yugo NAGATA" <nagata@sraoss.co.jp>, "PostgreSQL Hackers" <pgsql-hackers@lists.postgresql.org>
Date: 2026-03-16T02:39:21Z
Lists: pgsql-hackers 

At 2026-03-13 21:50:07, "Fujii Masao" <masao.fujii@gmail.com> wrote:
>On Fri, Mar 13, 2026 at 2:51 PM Yi Ding <dingyi_yale@163.com> wrote:
>> The new test added in v1 makes sense to me. A small suggestion is that to verify if a field is really null, we can do:
>>
>> ALTER FOREIGN TABLE agg_bad OPTIONS (ADD on_error 'set_null');
>> SELECT a, b IS NULL FROM agg_bad;
>
>Since the file_fdw test runs "\pset null _null_", a NULL value is displayed as
>"_null_". So you can verify that the value is NULL by checking whether
>"_null_" is shown.
>
>One could argue that this cannot be distinguished from the literal text value
>"_null_". However, relying on "\pset null _null_" is sufficient for this test,
>I think.
>
>Regards,
>
>-- 
>Fujii Masao

>


Sounds reasonable,that addressed my comment.


Regards,
Yi Ding

Commits

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

  1. file_fdw: Add regression test for file_fdw with ON_ERROR='set_null'

  2. Add COPY (on_error set_null) option

  3. Add REJECT_LIMIT option to the COPY command.

  4. Add log_verbosity = 'silent' support to COPY command.

  5. Add new COPY option LOG_VERBOSITY.