From: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | postgresql-common breaks logrotate |
Date: | 2013-12-26 23:11:10 |
Message-ID: | 52BCB78E.7040707@pinpointresearch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
People who have attempted to install PGDG versions of PostgreSQL on
recent Ubuntu releases have run into the cascading problem of postgresql
wanting to destroy Ubuntu.
Based on the packaging:
postgresql depends on postgresql-common
postgresql-common breaks logrotate (>3.8)
ubuntu-standard depends on logrotate
profit?...
It appears the reason for the claimed breakage is a very slight update
to logrotate that requires one to tell logrotate about files/directories
with non-"standard" ownership/permissions. Getting logrotate to stop
complaining is trivially resolved by the user by adding a single "su"
directive to the /etc/logrotate.d/postgresql-common or by having
PostgreSQL log to syslog.
It seems that "breaks" is overkill and the hassle imposed by that
declaration far exceeds any benefit therefrom.
Thoughts?
Cheers,
Steve
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2013-12-27 03:39:40 | Re: pg_upgrade & tablespaces |
Previous Message | Sergey Konoplev | 2013-12-26 22:25:09 | Re: FATAL: index contains unexpected zero page at block |