Re: pub/sub - specifying optional parameters without values.

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: pub/sub - specifying optional parameters without values.
Дата
Msg-id 1075167.1675176543@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: pub/sub - specifying optional parameters without values.  (Amit Kapila <amit.kapila16@gmail.com>)
Ответы RE: pub/sub - specifying optional parameters without values.  ("houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com>)
Список pgsql-hackers
Amit Kapila <amit.kapila16@gmail.com> writes:
> On Tue, Jan 31, 2023 at 4:25 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Hmph.  I generally think that options defined like this (it's a boolean,
>> except it isn't) are a bad idea, and would prefer to see that API
>> rethought while we still can.

> We have discussed this during development and considered using a
> separate option like parallel = on (or say parallel_workers = n) but
> there were challenges with the same. See discussion in email [1]. We
> also checked that we have various other places using something similar
> for options. For example COPY commands option: HEADER [ boolean |
> MATCH ].

Yeah, and it's bad experiences with the existing cases that make me
not want to add more.  Every one of those was somebody taking the
easy way out.  It generally leads to parsing oddities, such as
not accepting all the same spellings of "boolean" as before.

            regards, tom lane



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Assert fcinfo has enough args before allowing parameter access (was: Re: generate_series for timestamptz and time zone problem)
Следующее
От: Ashutosh Bapat
Дата:
Сообщение: Re: Logical replication timeout problem