From: | David Steele <david(at)pgmasters(dot)net> |
---|---|
To: | Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <stark(at)mit(dot)edu>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Reopen logfile on SIGHUP |
Date: | 2018-03-28 17:46:02 |
Message-ID: | 1f7fd09b-6838-2d6b-44ed-b5e4487de206@pgmasters.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2/27/18 8:54 PM, Michael Paquier wrote:
> On Tue, Feb 27, 2018 at 05:52:20PM -0500, Tom Lane wrote:
>> It already does treat SIGUSR1 as a log rotation request. Apparently
>> the point of this patch is that some people don't find that easy enough
>> to use, which is fair, because finding out the collector's PID from
>> outside isn't very easy.
>
> True enough. The syslogger does not show up in pg_stat_activity either,
> so I think that being able to do so would help for this case.
There does not seem to be any consensus on this patch so I'm marking it
Waiting on Author for the time being. At the end of the CF I'll mark it
Returned with Feedback if there is no further activity.
Regards,
--
-David
david(at)pgmasters(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Emre Hasegeli | 2018-03-28 17:50:16 | Re: Standby corruption after master is restarted |
Previous Message | Konstantin Knizhnik | 2018-03-28 17:36:32 | Re: disable SSL compression? |