Re: Prevent printing "next step instructions" in initdb and pg_upgrade
| От | Bruce Momjian |
|---|---|
| Тема | Re: Prevent printing "next step instructions" in initdb and pg_upgrade |
| Дата | |
| Msg-id | 20210207145014.GA18363@momjian.us обсуждение |
| Ответ на | Re: 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
|
| Список | pgsql-hackers |
On Sun, Feb 7, 2021 at 11:21:05AM +0100, Magnus Hagander wrote: > > It appears that there is an extra blank line in the initdb output before > > "Success" now. > > Oops, clearly it does. > > That said, the full output is: > > """ > Success. You can now start the database server using: > > bin/pg_ctl -D /tmp/data -l logfile start > > > Success. > """ > > Isn't the whole "Success." at the end redundant here, and we should > just end the message after the pg_ctl command? So not just the extra > newline, but the whole thing? Agreed. -- Bruce Momjian <bruce@momjian.us> https://momjian.us EDB https://enterprisedb.com The usefulness of a cup is in its emptiness, Bruce Lee
В списке pgsql-hackers по дате отправления: