Postgres Pro
Downloads
Home   >   mailing lists

Re: [PATCH] Log PostgreSQL version number on startup - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [PATCH] Log PostgreSQL version number on startup
Date
Msg-id d5d50936-20b9-85f1-06bc-94a01c5040c1@2ndquadrant.com
Whole thread Raw
In response to [PATCH] Log PostgreSQL version number on startup  (Christoph Berg <christoph.berg@credativ.de>)
Responses Re: [PATCH] Log PostgreSQL version number on startup  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
Tree view 
On 21/11/2018 15:46, Christoph Berg wrote:
> A startup looks like this:
> 
> 2018-11-21 15:19:47.259 CET [24453] LOG:  listening on IPv6 address "::1", port 5431
> 2018-11-21 15:19:47.259 CET [24453] LOG:  listening on IPv4 address "127.0.0.1", port 5431
> 2018-11-21 15:19:47.315 CET [24453] LOG:  listening on Unix socket "/tmp/.s.PGSQL.5431"
> 2018-11-21 15:19:47.394 CET [24453] LOG:  starting PostgreSQL 12devel on x86_64-pc-linux-gnu, compiled by gcc (Debian
8.2.0-9)8.2.0, 64-bit
 
> 2018-11-21 15:19:47.426 CET [24454] LOG:  database system was shut down at 2018-11-21 15:15:35 CET
> 2018-11-21 15:19:47.460 CET [24453] LOG:  database system is ready to accept connections
> 
> (I'd rather put the start message before the listening messages, but I
> think the startup message should be logged via logging_collector, and
> listening is logged before the log file is opened.)

Why don't we start the logging collector before opening the sockets?

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Use atexit() in initdb and pg_basebackup
Next
From: Peter Eisentraut
Date:
Subject: Re: [proposal] Add an option for returning SQLSTATE in psql errormessage