Re: [HACKERS] [COMMITTERS] pgsql: Improve postmaster's logging oflisten socket creation. - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [HACKERS] [COMMITTERS] pgsql: Improve postmaster's logging oflisten socket creation.
Date
Msg-id 20170313153123.snaadbjuiwxhgc73@alvherre.pgsql
Whole thread Raw
In response to Re: [HACKERS] [COMMITTERS] pgsql: Improve postmaster's logging of listen socket creation.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses 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 oflisten socket creation.  (Stephen Frost <sfrost@snowman.net>)
List 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 by date:

Previous
From: David Steele
Date:
Subject: Re: [HACKERS] tuplesort_gettuple_common() and *should_free argument
Next
From: Aleksander Alekseev
Date:
Subject: Re: [HACKERS] [PATCH] Suppress Clang 3.9 warnings