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

From: Zhang Mingli <zmlpostgres(at)gmail(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: [Refactor]Avoid to handle FORCE_NOT_NULL/FORCE_NULL options when COPY TO
Date: 2022-07-26 16:16:33
Message-ID: F28F0B5A-766F-4D33-BF44-43B3A052D833@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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 <https://github.com/postgres/postgres//commit/c532d15dddff14b01fe9ef1d465013cb8ef186df> .

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

Regards,
Zhang Mingli

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2022-07-26 16:22:31 Re: remove more archiving overhead
Previous Message Tom Lane 2022-07-26 16:14:19 Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands