[BUGS] BUG #14851: Systemd kills long-running recovery - Mailing list pgsql-bugs

From gdr@gdr.name
Subject [BUGS] BUG #14851: Systemd kills long-running recovery
Date
Msg-id 20171013091028.20254.74268@wrigleys.postgresql.org
Whole thread Raw
Responses Re: [BUGS] BUG #14851: Systemd kills long-running recovery  (Fabrízio de Royes Mello <fabriziomello@gmail.com>)
Re: [BUGS] BUG #14851: Systemd kills long-running recovery  (John R Pierce <pierce@hogranch.com>)
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      14851
Logged by:          GDR !
Email address:      gdr@gdr.name
PostgreSQL version: 9.6.5
Operating system:   CentOS 7 / pgdg
Description:

Summary: I think the line "TimeoutSec=300" in the systemd unit file isn't
necessary

Problem: I'm running a Postgres replication slave  fresh after
pg_basebackup. It has about 12 hours worth of xlogs to replay.  After 5
minutes of "systemctl start postgresql-9.6" not returning to shell, systemd
kills the server in the middle of recovery.

This is because of TimeoutSec=300 in the systemd unit file. I don't think
removing this statement will have any negative effects and I propose that
it's not included in the pgdg distribution.


--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [BUGS] BUG #14849: jsonb_build_object doesn't like VARIADIC callsvery much
Next
From: alexey.ermakov@dataegret.com
Date:
Subject: [BUGS] BUG #14852: Refreshing materialized view might lead to a problem"could not access status of transaction"