From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, 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-14 11:37:01 |
Message-ID: | 20170314113701.GL9812@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > 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
>
> Yeah, I've been thinking that maybe it should look like
>
> 2017-03-13 10:08:49.399 EDT [90059] LOG: listening on IPv6 address "::1", port 5432
> 2017-03-13 10:08:49.399 EDT [90059] LOG: listening on IPv4 address "127.0.0.1", port 5432
> 2017-03-13 10:08:49.400 EDT [90059] LOG: listening on Unix address "/tmp/.s.PGSQL.5432"
>
> It would take a couple more lines of code to make that happen, but
> it would future-proof the messages against the day we decide to
> allow one server to respond to more than one port number ...
I certainly agree with adding the port for TCP. I also agree with
Andres' point about the unix socket, though I'm tempted to suggest that
we should just teach libpq to understand a straight unix socket being
passed for host/-h rather than change what the server reports here..
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-03-14 11:49:51 | pgsql: Remove some bogus logic from create_gather_merge_plan. |
Previous Message | Michael Paquier | 2017-03-14 06:18:43 | Re: [COMMITTERS] pgsql: Add test case for two phase commit. Also by Masahiko Sawada. |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2017-03-14 11:44:24 | Re: WIP: Faster Expression Processing v4 |
Previous Message | Alvaro Herrera | 2017-03-14 11:28:02 | Re: WIP: Faster Expression Processing v4 |