Re: [COMMITTERS] pgsql: Improve postmaster's logging of listen socket creation.

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Improve postmaster's logging of listen socket creation.
Date: 2017-03-13 15:31:23
Message-ID: 20170313153123.snaadbjuiwxhgc73@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2017-03-13 15:37:50 Re: [COMMITTERS] pgsql: Improve postmaster's logging of listen socket creation.
Previous Message Tom Lane 2017-03-13 14:19:37 Re: [COMMITTERS] pgsql: Improve postmaster's logging of listen socket creation.

Browse pgsql-hackers by date

  From Date Subject
Next Message Aleksander Alekseev 2017-03-13 15:35:53 Re: [PATCH] Suppress Clang 3.9 warnings
Previous Message David Steele 2017-03-13 15:23:12 Re: tuplesort_gettuple_common() and *should_free argument