Re: Reopen logfile on SIGHUP - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Reopen logfile on SIGHUP
Date
Msg-id CAKFQuwbi5FyAm_9t3EGkDkJ=A2Fus-9NV_ApEBMtrwwP=5P9_Q@mail.gmail.com
Whole thread Raw
In response to Re: Reopen logfile on SIGHUP  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Reopen logfile on SIGHUP  (Andres Freund <andres@anarazel.de>)
Re: Reopen logfile on SIGHUP  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Feb 27, 2018 at 4:12 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
IOW, I think a fair response to this is "if you're using logrotate with
Postgres, you're doing it wrong".  That was of some use back before we
spent so much sweat on the syslogger, but it's not a reasonable setup
today.

A couple of weeks ago a message was posted to general [1] in which I concluded the desired behavior is not supported natively.  I'm curious whether better advice than mine can be given ...


David J.

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Sigh, I broke crake again
Next
From: Andres Freund
Date:
Subject: Re: Reopen logfile on SIGHUP