| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Christoph Berg <christoph(dot)berg(at)credativ(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Log PostgreSQL version number on startup |
| Date: | 2019-01-30 22:29:41 |
| Message-ID: | 7490cb77-7e38-ccb2-d862-3c94408236fc@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 29/01/2019 16:46, Christoph Berg wrote:
> Re: Peter Eisentraut 2019-01-16 <92bfdfdf-4164-aec5-4e32-c26e67821c38(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2019-01-30 22:49:25 | Re: pg_dump multi VALUES INSERT |
| Previous Message | David Rowley | 2019-01-30 19:32:16 | Re: speeding up planning with partitions |