| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Joe Conway <mail(at)joeconway(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Upgrading postmaster's log messages about bind/listen errors |
| Date: | 2017-03-10 19:24:54 |
| Message-ID: | d9f99ab3-5295-a242-2b71-4c1a7965fee1@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/9/17 23:43, Tom Lane wrote:
> However, if we're measuring this on a scale of usefulness to the average
> DBA, I would argue that it's of more interest than any of these messages
> that currently appear by default:
>
> 2017-03-09 23:40:12.334 EST [19335] LOG: MultiXact member wraparound protections are now enabled
> 2017-03-09 23:40:12.335 EST [19339] LOG: autovacuum launcher started
> 2017-03-09 23:40:12.336 EST [19341] LOG: logical replication launcher started
>
> The first of those is surely past its sell-by date. As for the other two,
> we should log *failure* to start, but not the normal case.
I'm OK with removing these. No news is good news.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2017-03-10 19:28:03 | Re: SQL/JSON in PostgreSQL |
| Previous Message | Andres Freund | 2017-03-10 19:24:33 | Re: WIP: Faster Expression Processing v4 |