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

From Andres Freund
Subject Re: Reopen logfile on SIGHUP
Date
Msg-id 20180227233918.dyqg5lx5edfmwz2l@alap3.anarazel.de
Whole thread Raw
In response to Re: Reopen logfile on SIGHUP  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-hackers
On 2018-02-27 16:20:28 -0700, David G. Johnston wrote:
> 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 ...
> 
>
https://www.postgresql.org/message-id/flat/CAKoQ0XHAy9De1C8gxUWHSW6w5iKcqX03wyWGe_%2Bc8NxJccCBHw%40mail.gmail.com#CAKoQ0XHAy9De1C8gxUWHSW6w5iKcqX03wyWGe_+c8NxJccCBHw@mail.gmail.com

That link appears to be broken. Real one
https://www.postgresql.org/message-id/CAKoQ0XHAy9De1C8gxUWHSW6w5iKcqX03wyWGe_+c8NxJccCBHw@mail.gmail.com


pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Reopen logfile on SIGHUP
Next
From: Tom Lane
Date:
Subject: Re: Reopen logfile on SIGHUP