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

From: Mingli Zhang <zmlpostgres(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, guofenglinux(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [Refactor]Avoid to handle FORCE_NOT_NULL/FORCE_NULL options when COPY TO
Date: 2022-11-01 15:45:45
Message-ID: CANG7CALpB74xzAWUA53sNip-pa1q8mgpWFwzDBj3F+P1GxdCkg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

>

> The point about cleaning up the attribute handling of FORCE_NOT_NULL
> and FORCE_NULL in the COPY TO path is a good catch, though, so let's
> remove all that. I'll go apply this part of the patch in a bit, or
> tomorrow.
> --
> Michael

Thanks for review!

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-11-01 15:59:04 Re: heavily contended lwlocks with long wait queues scale badly
Previous Message Andres Freund 2022-11-01 15:42:51 Re: ResourceOwner refactoring