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

From Joshua D. Drake
Subject Re: Reopen logfile on SIGHUP
Date
Msg-id 492687ea-9a8f-7a17-0f98-f579dec0f7ee@commandprompt.com
Whole thread Raw
In response to Re: Reopen logfile on SIGHUP  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 04/10/2018 12:17 PM, Tom Lane wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> 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.
> 
> We, as in the core project, are not shipping it.

Well, yes we are at least from an external perception problem. The name 
says it all, PGDG RPMs. They are either the official PostgreSQL.Org RPMs 
or they aren't. If they aren't they shouldn't be called PGDG RPMs nor 
should they be available from yum.postgresql.org and apt.postgresql.org 
respectively.

Note: I am not advocating the removal of those packages. I am advocating 
that the core project of PostgreSQL.Org in fact does ship those packages 
and that is how people see it outside of our email silo.

JD



-- 
Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc
***  A fault and talent of mine is to tell it exactly how it is.  ***
PostgreSQL centered full stack support, consulting and development.
Advocate: @amplifypostgres || Learn: https://postgresconf.org
*****     Unless otherwise stated, opinions are my own.   *****


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: 2018-03 CF Cleanup
Next
From: Robert Haas
Date:
Subject: Re: Reopen logfile on SIGHUP