Postgres Pro
Downloads
Home   >   mailing lists

[Refactor]Avoid to handle FORCE_NOT_NULL/FORCE_NULL options when COPY TO - Mailing list pgsql-hackers

From Zhang Mingli
Subject [Refactor]Avoid to handle FORCE_NOT_NULL/FORCE_NULL options when COPY TO
Date
Msg-id F28F0B5A-766F-4D33-BF44-43B3A052D833@gmail.com
Whole thread Raw
Responses Re: [Refactor]Avoid to handle FORCE_NOT_NULL/FORCE_NULL options when COPY TO
List pgsql-hackers
Tree view
Hi,


FORCE_NOT_NULL and FORCE_NULL are only used when COPY FROM.

And copyto.c and copyfrom.c are split in this commit https://github.com/postgres/postgres//commit/c532d15dddff14b01fe9ef1d465013cb8ef186df .

There is no need to handle these options when COPY TO.


Regards,
Zhang Mingli



Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Unprivileged user can induce crash by using an SUSET param in PGOPTIONS
Next
From: Nathan Bossart
Date:
Subject: Re: remove more archiving overhead