Re: [PATCH] Log PostgreSQL version number on startup

2019-01-30 Thread Peter Eisentraut
On 29/01/2019 16:46, Christoph Berg wrote: > Re: Peter Eisentraut 2019-01-16 > <92bfdfdf-4164-aec5-4e32-c26e67821...@2ndquadrant.com> >>> Why don't we start the logging collector before opening the sockets? >> >> Specifically, something like the attached. >> >> This keeps the dynamic module loadin

Re: [PATCH] Log PostgreSQL version number on startup

2019-01-29 Thread Christoph Berg
Re: Peter Eisentraut 2019-01-16 <92bfdfdf-4164-aec5-4e32-c26e67821...@2ndquadrant.com> > > Why don't we start the logging collector before opening the sockets? > > Specifically, something like the attached. > > This keeps the dynamic module loading before the logging collector > start, so we see

Re: [PATCH] Log PostgreSQL version number on startup

2019-01-16 Thread Peter Eisentraut
On 05/01/2019 15:53, Peter Eisentraut wrote: > 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.

Re: [PATCH] Log PostgreSQL version number on startup

2019-01-05 Thread Peter Eisentraut
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]

Re: [PATCH] Log PostgreSQL version number on startup

2019-01-04 Thread Michael Paquier
On Fri, Jan 04, 2019 at 06:54:51PM -0500, Stephen Frost wrote: > * Peter Eisentraut (peter.eisentr...@2ndquadrant.com) wrote: >> Do we want to do the whole version string, or just "PostgreSQL 12devel"? > > The whole thing. I would prefer the whole string as well, as that's useful to look after al

Re: [PATCH] Log PostgreSQL version number on startup

2019-01-04 Thread Stephen Frost
Greetings, * Peter Eisentraut (peter.eisentr...@2ndquadrant.com) wrote: > On 21/11/2018 15:46, Christoph Berg wrote: > > 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 > > Do we want to do the whole

Re: [PATCH] Log PostgreSQL version number on startup

2019-01-02 Thread Peter Eisentraut
On 21/11/2018 15:46, Christoph Berg wrote: > 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 Do we want to do the whole version string, or just "PostgreSQL 12devel"? -- Peter Eisentraut h

Re: [PATCH] Log PostgreSQL version number on startup

2018-12-10 Thread Christoph Berg
Re: Michael Paquier 2018-12-10 <20181210063307.gd1...@paquier.xyz> > On Wed, Nov 21, 2018 at 11:32:46AM -0500, Stephen Frost wrote: > > * Christoph Berg (christoph.b...@credativ.de) wrote: > >> it has bugged me for a long time that there's no clear "PostgreSQL is > >> starting" message in the serve

Re: [PATCH] Log PostgreSQL version number on startup

2018-12-09 Thread Michael Paquier
On Wed, Nov 21, 2018 at 11:32:46AM -0500, Stephen Frost wrote: > * Christoph Berg (christoph.b...@credativ.de) wrote: >> it has bugged me for a long time that there's no clear "PostgreSQL is >> starting" message in the server log file. I'd like to change that for >> two reasons: > > +1 +1. One c

Re: [PATCH] Log PostgreSQL version number on startup

2018-11-21 Thread Stephen Frost
Greetings, * Christoph Berg (christoph.b...@credativ.de) wrote: > it has bugged me for a long time that there's no clear "PostgreSQL is > starting" message in the server log file. I'd like to change that for > two reasons: +1 > * when reading a long log file, it's not entirely clear where a new

[PATCH] Log PostgreSQL version number on startup

2018-11-21 Thread Christoph Berg
mpeterallee 108, 41189 Mönchengladbach Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer Unser Umgang mit personenbezogenen Daten unterliegt folgenden Bestimmungen: https://www.credativ.de/datenschutz >From 49f786a26110ca55d12c47f75e8662047e78c5c8 Mon Sep 17 00:00:00 2001 From: Christop