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

From Robert Haas
Subject Re: Reopen logfile on SIGHUP
Date
Msg-id CA+TgmoZfYrBmLA8ovwoa22DoLbbxrmcxqroMZZPeacLf7sXXgw@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  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Feb 27, 2018 at 6: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".

Well, the original post says that this is how the PGDG RPMs are doing
it on Debian/Ubuntu.  I wonder if that's due to some Debian/Ubuntu
policy or just a preference on the part of whoever did the packaging
work.  Anyway it's a little hard to argue that the configuration is
insane when we're shipping it.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: [sqlsmith] Segfault in expand_tuple
Next
From: Alvaro Herrera
Date:
Subject: Re: pgsql: Support partition pruning at execution time