Re: Better error message when --single is not the first arg to postgres executable

Поиск
Список
Период
Сортировка
От Greg Sabino Mullane
Тема Re: Better error message when --single is not the first arg to postgres executable
Дата
Msg-id CAKAnmmKb-zDo=Xn5XdM0D5hEzO=uYEh58R_7xt8T-1mci5akyg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Better error message when --single is not the first arg to postgres executable  (Nathan Bossart <nathandbossart@gmail.com>)
Ответы Re: Better error message when --single is not the first arg to postgres executable
Список pgsql-hackers
Дерево обсуждения
On Wed, Jun 5, 2024 at 3:18 PM Nathan Bossart <nathandbossart@gmail.com> wrote:
Could we remove the requirement that --single must be first?  I'm not thrilled about adding a list of "must be first" options that needs to stay updated, but given this list probably doesn't change too frequently, maybe that's still better than a more invasive patch to allow specifying these options in any order...

It would be nice, and I briefly looked into removing the "first" requirement, but src/backend/tcop/postgres.c for one assumes that --single is always argv[1], and it seemed not worth the extra effort to make it work for argv[N] instead of argv[1]. I don't mind it being the first argument, but that confusing error message needs to go.

Thanks,
Greg

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

Предыдущее
От: "Hayato Kuroda (Fujitsu)"
Дата:
Сообщение: RE: Pgoutput not capturing the generated columns
Следующее
От: Greg Sabino Mullane
Дата:
Сообщение: Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs