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 7490cb77-7e38-ccb2-d862-3c94408236fc@2ndquadrant.com
Whole thread Raw
In response to Re: [PATCH] Log PostgreSQL version number on startup  (Christoph Berg <christoph.berg@credativ.de>)
List pgsql-hackers
On 29/01/2019 16:46, Christoph Berg wrote:
> Re: Peter Eisentraut 2019-01-16 <92bfdfdf-4164-aec5-4e32-c26e67821c38@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 those error messages on stderr, but then the setting up
>> of the sockets would get logged.
> 
> This works nicely, so +1.
> 
> I'm attaching your patch as 0001 and my rebased one on top of it as
> 0002.

committed

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


pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: speeding up planning with partitions
Next
From: David Rowley
Date:
Subject: Re: pg_dump multi VALUES INSERT