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

Zhang Mingli <zmlpostgres@gmail.com>

From: Zhang Mingli <zmlpostgres@gmail.com>

To: pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2022-07-26T16:16:33Z

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

Commits

Remove code handling FORCE_NULL and FORCE_NOT_NULL for COPY TO
- 8e621c10c73a 16.0 landed
Add more tests for COPY with incorrect option combinations
- 451d1164b9d0 16.0 landed
Split copy.c into four files.
- c532d15dddff 14.0 cited