Re: file_fdw: Support multi-line HEADER option.

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Steven Niu <niushiji(at)gmail(dot)com>
Cc: Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Shinya Kato <shinya11(dot)kato(at)gmail(dot)com>, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: file_fdw: Support multi-line HEADER option.
Date: 2026-01-22 01:18:08
Message-ID: CAHGQGwHUyyZMWEY+T6-3kRLE1uwJhUeeKOFpfM_AW4RipxNQNg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jan 21, 2026 at 5:18 PM Steven Niu <niushiji(at)gmail(dot)com> wrote:
> I've noticed an inconsistent naming convention in the patch:
> we use a capitalized Boolean for the boolean type, but a lowercase integer when referring to the value type.
>
> + errmsg("%s requires a Boolean value, an integer "
> + "value greater than or equal to zero
>
> Is there any reason why we follow this mixed style?

I don't have a strong opinion on this. "Boolean value" has been used in command
error messages from before, and I couldn't find any messages that use the term
"Integer". So I committed the patch with the original wording. If this turns out
to be an issue, we can revisit it later.

> Another nitpick in v6-0001 patch:
> tow whitespaces are between "special" and "value"
> + second %s is the special value "match" for that option */

Thanks for catching that! I've fixed it.

I've pushed the patches. Thanks!

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sami Imseih 2026-01-22 01:41:30 Re: Flush some statistics within running transactions
Previous Message Michael Paquier 2026-01-22 00:48:35 Re: Having problems generating a code coverage report