Re: Prevent printing "next step instructions" in initdb and pg_upgrade

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: Prevent printing "next step instructions" in initdb and pg_upgrade
Дата
Msg-id df2b2919-6e85-41ca-6570-3ae8ff86d889@2ndquadrant.com
обсуждение исходный текст
Ответ на Prevent printing "next step instructions" in initdb and pg_upgrade  (Magnus Hagander <magnus@hagander.net>)
Ответы Re: Prevent printing "next step instructions" in initdb and pg_upgrade  (Bruce Momjian <bruce@momjian.us>)
Список pgsql-hackers
On 2020-10-06 12:26, Magnus Hagander wrote:
> I went with the name --no-instructions to have the same name for both 
> initdb and pg_upgrade. The downside is that "no-instructions" also 
> causes the scripts not to be written in pg_upgrade, which arguably is a 
> different thing. We could go with "--no-instructions" and 
> "--no-scripts", but that would leave the parameters different. I also 
> considered "--no-next-step", but that one didn't quite have the right 
> ring to me. I'm happy for other suggestions on the parameter names.

What scripts are left after we remove the analyze script, as discussed 
in a different thread?

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



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

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: pg_upgrade analyze script
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: "unix_socket_directories" should be GUC_LIST_INPUT?