Re: Reject HEADER with binary and json COPY formats by option presence

On Wed, Jun 3, 2026 at 2:24 PM Shinya Kato <shinya11(dot)kato(at)gmail(dot)com> wrote:
>
> On Sun, May 31, 2026 at 10:57 AM Chao Li <li(dot)evan(dot)chao(at)gmail(dot)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