Quick Links

Re: [Refactor]Avoid to handle FORCE_NOT_NULL/FORCE_NULL options when COPY TO

From:	Richard Guo <guofenglinux(at)gmail(dot)com>
To:	Zhang Mingli <zmlpostgres(at)gmail(dot)com>
Cc:	Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject:	Re: [Refactor]Avoid to handle FORCE_NOT_NULL/FORCE_NULL options when COPY TO
Date:	2022-07-29 03:23:57
Message-ID:	CAMbWs49Wiwk6v_iDuSiDNjF6j-D+ynKUwUw=OAv+Kvdjbmq76A@mail.gmail.com
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-hackers

On Thu, Jul 28, 2022 at 9:04 PM Zhang Mingli <zmlpostgres(at)gmail(dot)com> wrote:

> Assertions added.
>

Can we also add assertions to make sure force_quote, force_notnull and
force_null are available only in CSV mode?

Thanks
Richard

In response to

Re: [Refactor]Avoid to handle FORCE_NOT_NULL/FORCE_NULL options when COPY TO at 2022-07-28 13:04:04 from Zhang Mingli

Responses

Re: [Refactor]Avoid to handle FORCE_NOT_NULL/FORCE_NULL options when COPY TO at 2022-08-01 01:59:49 from Zhang Mingli

Browse pgsql-hackers by date

	From	Date	Subject
Next Message	Amit Kapila	2022-07-29 03:29:07	Re: Functions 'is_publishable_class' and 'is_publishable_relation' should stay together.
Previous Message	Peter Smith	2022-07-29 03:01:30	Re: Handle infinite recursion in logical replication setup