Luckily no one else is running automatic yum update every morning on their production postgresql-database ¯\_(ツ)_/¯ :D
// Patrik
On Tue, Dec 12, 2017 at 6:26 PM Devrim Gündüz <devrim@gunduz.org> wrote:
Hi,
On Tue, 2017-12-12 at 10:00 +0000, martinsson.patrik@gmail.com wrote: > The following bug has been logged on the website: > > Bug reference: 14967 > Logged by: Patrik Martinsson > Email address: martinsson.patrik@gmail.com > PostgreSQL version: 9.3.20 > Operating system: CentOS 7.4.1708 > Description: > > Hi, > > I'm not sure where the "bug" lies here, but I just noticed that running an > yum update from postgresql93-9.3.20-1PGDG.rhel7.x86_64 -> > 9.3.20-3PGDG.rhel7.x86_64 makes postgresql impossible to start through > systemd. > > The issue seems to be related to the parameter "TimeoutSec=infinity" in > /usr/lib/systemd/system/postgresql-9.3.service.
<snip>
You are right. A test commit accidentally went into prod repos. Apologies for that. I just pushed updated packages to repos. yum update will fix the issue.
Regards, -- Devrim Gündüz EnterpriseDB: https://www.enterprisedb.com PostgreSQL Consultant, Red Hat Certified Engineer Twitter: @DevrimGunduz , @DevrimGunduzTR
