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

From Fujii Masao
Subject Re: Re: Change COPY ... ON_ERROR ignore to ON_ERROR ignore_row
Date
Msg-id CAHGQGwHGyBAA6e+2eMzOPAbwd9CHKhCCKQ8AVHXG2UwUEj7zew@mail.gmail.com
Whole thread
In response to Re:Re: Change COPY ... ON_ERROR ignore to ON_ERROR ignore_row  ("Yi Ding" <dingyi_yale@163.com>)
Responses Re:Re: Re: Change COPY ... ON_ERROR ignore to ON_ERROR ignore_row
List pgsql-hackers
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



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: IS JSON predicate support for domain base type as JSON/JSONB/BYTEA/TEXT
Next
From: Peter Eisentraut
Date:
Subject: Re: support create index on virtual generated column.