Postgres Pro
Downloads
Home   >   mailing lists

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

From Andres Freund
Subject Re: [HACKERS] [COMMITTERS] pgsql: Improve postmaster's logging oflisten socket creation.
Date
Msg-id 20170314033842.st7gifec55yigz2h@alap3.anarazel.de
Whole thread Raw
In response to Re: [HACKERS] [COMMITTERS] pgsql: Improve postmaster's logging of listen socket creation.  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [HACKERS] [COMMITTERS] pgsql: Improve postmaster's logging of listen socket creation.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
On 2017-03-13 10:12:42 -0400, Robert Haas wrote:
> 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 don't mind the new output, but I kinda wonder whether it's a good idea
to include the '.s.PGSQL.5432' bit in the host and/or whether we
shouldn't include the port in the TCP cases as well

One cannot use -h /tmp/.s.PGSQL.5432, making this a bit confusing...

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] scram and \password
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] [COMMITTERS] pgsql: Improve postmaster's logging of listen socket creation.