Re: Prevent printing "next step instructions" in initdb and pg_upgrade
| От | Magnus Hagander |
|---|---|
| Тема | Re: Prevent printing "next step instructions" in initdb and pg_upgrade |
| Дата | |
| Msg-id | CABUevEwegSS9EHiEOBynodR3H-s1_-gCJ6FZ4gYx5E5V__=0gA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Prevent printing "next step instructions" in initdb and pg_upgrade (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Prevent printing "next step instructions" in initdb and pg_upgrade
|
| Список | pgsql-hackers |
On Tue, Oct 6, 2020 at 4:31 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Magnus Hagander <magnus@hagander.net> writes:
> The use case for this is for example the debian or redhat package wrappers.
> When these commands are run under those wrappers the printed instructions
> are *wrong*. It's better in that case to exclude them, and let the wrapper
> be responsible for printing the correct instructions.
Hm, does it matter? I think those wrappers send the output to /dev/null
anyway.
The debian ones don't, because they consider it useful information to the user. I'd say that it is, especially in the case of pg_upgrade. (Less so about initdb, but still a bit -- especially when creating secondary clusters)
The redhat ones I believe sent it to a logfile, not to /dev/null. Meaning it's not in your face, but it still contains incorrect instructions.
В списке pgsql-hackers по дате отправления: