Re: [HACKERS] [COMMITTERS] pgsql: Improve postmaster's logging oflisten socket creation.
От | Alvaro Herrera |
---|---|
Тема | Re: [HACKERS] [COMMITTERS] pgsql: Improve postmaster's logging oflisten socket creation. |
Дата | |
Msg-id | 20170313153123.snaadbjuiwxhgc73@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: [HACKERS] [COMMITTERS] pgsql: Improve postmaster's logging of listen socket creation. (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [HACKERS] [COMMITTERS] pgsql: Improve postmaster's logging of listen socket creation.
Re: [HACKERS] [COMMITTERS] pgsql: Improve postmaster's logging oflisten socket creation. |
Список | pgsql-hackers |
Tom Lane wrote: > 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. I think it's good to have it, but I would argue that it should be a single line that lists all the addresses instead. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: