Request a Demo
Home   >   mailing lists

Re: Reject HEADER with binary and json COPY formats by option presence - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Reject HEADER with binary and json COPY formats by option presence
Date
Msg-id CAHGQGwEU7507_wFSkzHdHrmK5nnuWremdRgAzEkk0ft1kUrHbw@mail.gmail.com
Whole thread
In response to Re: Reject HEADER with binary and json COPY formats by option presence  (Shinya Kato <shinya11.kato@gmail.com>)
Responses Re: Reject HEADER with binary and json COPY formats by option presence
List pgsql-hackers
Tree view 
On Wed, Jun 3, 2026 at 2:24 PM Shinya Kato <shinya11.kato@gmail.com> wrote:
>
> On Sun, May 31, 2026 at 10:57 AM Chao Li <li.evan.chao@gmail.com> wrote:
>
> > While testing “file_fdw: Support multi-line HEADER option”, I noticed a small issue.
>
> Thanks for reporting this!

I'm not yet convinced that this needs a code change. We already seem to have
both styles today: some options are rejected based on their presence,
while others are effectively judged based on whether the specified value
actually enables the feature. I don't think we have a clear rule that
everything should be presence-based.

Regards,

--
Fujii Masao

pgsql-hackers by date:

Previous
From: "Maksim.Melnikov"
Date:
Subject: Re: Init connection time grows quadratically
Next
From: jian he
Date:
Subject: Re: Fix bug of CHECK constraint enforceability recursion