Skip site navigation (1) Skip section navigation (2)

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

From: Andres Freund <andres(at)anarazel(dot)de>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,"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-14 03:38:42
Message-ID: 20170314033842.st7gifec55yigz2h@alap3.anarazel.de (view raw, whole thread or download thread mbox)
Thread:
Lists: pgsql-committerspgsql-hackers
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...


In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2017-03-14 03:43:13
Subject: Re: [COMMITTERS] pgsql: Improve postmaster's logging of listen socket creation.
Previous:From: Tom LaneDate: 2017-03-14 03:34:14
Subject: Re: scram and \password

pgsql-committers by date

Next:From: Tom LaneDate: 2017-03-14 03:43:13
Subject: Re: [COMMITTERS] pgsql: Improve postmaster's logging of listen socket creation.
Previous:From: Tom LaneDate: 2017-03-13 23:06:33
Subject: pgsql: Fix busted markup.

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group