Quick Links

Re: [feature]COPY FROM enable FORCE_NULL/FORCE_NOT_NULL on all columns

From:	Andrew Dunstan <andrew(at)dunslane(dot)net>
To:	Zhang Mingli <zmlpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject:	Re: [feature]COPY FROM enable FORCE_NULL/FORCE_NOT_NULL on all columns
Date:	2022-08-01 19:50:58
Message-ID:	62d003fa-3ff4-cc2d-fee1-c4fcbd757ff3@dunslane.net
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-hackers

On 2022-08-01 Mo 09:56, Zhang Mingli wrote:
> Hi,
>
> The previous discussion is:
>
> https://www.postgresql.org/message-id/CACJufxEnVqzOFtqhexF2%2BAwOKFrV8zHOY3y%3Dp%2BgPK6eB14pn_w%40mail.gmail.com

Starting a new thread is pointless and annoying. As I said in the
previous thread, we would need a patch.

cheers

andrew

--

Andrew Dunstan
EDB: https://www.enterprisedb.com

In response to

[feature]COPY FROM enable FORCE_NULL/FORCE_NOT_NULL on all columns at 2022-08-01 13:56:14 from Zhang Mingli

Responses

Re: [feature]COPY FROM enable FORCE_NULL/FORCE_NOT_NULL on all columns at 2022-08-01 19:53:11 from Andrew Dunstan

Browse pgsql-hackers by date

	From	Date	Subject
Next Message	Robert Haas	2022-08-01 19:51:03	Re: pg_auth_members.grantor is bunk
Previous Message	Tom Lane	2022-08-01 19:13:22	Re: enable/disable broken for statement triggers on partitioned tables