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

From: Zhang Mingli <zmlpostgres(at)gmail(dot)com>
To: Richard Guo <guofenglinux(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-08-01 01:59:49
Message-ID: f37d9295-9b21-4afa-86fd-7e88f9a169f4@Spark
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

HI,

More assertions added.

Thanks.

Regards,
Zhang Mingli
On Jul 29, 2022, 11:24 +0800, Richard Guo <guofenglinux(at)gmail(dot)com>, wrote:
>
> > 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

Attachment Content-Type Size
vn-0003-Avoid-to-handle-FORCE_NOT_NULL-FORCE_NULL-options.patch application/octet-stream 3.5 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-08-01 02:01:04 Re: standby recovery fails (tablespace related) (tentative patch and discussion)
Previous Message Julien Rouhaud 2022-08-01 01:47:21 Re: pg_buffercache: add sql test