Re: [HACKERS] [COMMITTERS] pgsql: Improve postmaster's logging of listen socket creation.
От | Tom Lane |
---|---|
Тема | Re: [HACKERS] [COMMITTERS] pgsql: Improve postmaster's logging of listen socket creation. |
Дата | |
Msg-id | 23987.1489414777@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [HACKERS] [COMMITTERS] pgsql: Improve postmaster's logging of listen socket creation. (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: [HACKERS] [COMMITTERS] pgsql: Improve postmaster's logging oflisten socket creation.
|
Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> writes: > So now on every startup I get this: > 2017-03-13 10:08:49.399 EDT [90059] LOG: listening on IPv6 address "::1" > 2017-03-13 10:08:49.399 EDT [90059] LOG: listening on IPv4 address "127.0.0.1" > 2017-03-13 10:08:49.400 EDT [90059] LOG: listening on Unix address > "/tmp/.s.PGSQL.5432" > I think the idea that this is worth three lines of log output (out of > a total of six) is hard to stomach. You were in the minority before on the usefulness of this output, and I think you still are. Personally I've already found it useful to be able to check that buildfarm runs are binding to (only) the addresses they're supposed to. Besides, unless someone has an objection to what I proposed in <17211.1489189214@sss.pgh.pa.us> concerning getting rid of the "MultiXact member wraparound protections are now enabled" message in the normal case, we'll have saved three other lines relative to where we were before, so that the net chattiness is the same. regards, tom lane
В списке pgsql-hackers по дате отправления: