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
