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

From John R Pierce
Subject Re: [BUGS] BUG #14851: Systemd kills long-running recovery
Date
Msg-id 81d229fd-02f7-13a2-47ab-3bb9435f4c7d@hogranch.com
Whole thread Raw
In response to [BUGS] BUG #14851: Systemd kills long-running recovery  (gdr@gdr.name)
Responses Re: [BUGS] BUG #14851: Systemd kills long-running recovery  (GDR! <gdr@gdr.name>)
List pgsql-bugs
On 10/13/2017 2:10 AM, gdr@gdr.name wrote:
> 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.


Maybe the unit code that detects the server is running needs some way of 
detecting its in recovery, and that the recovery is somehow progressing, 
and report that as 'running' ?


-- 
john r pierce, recycling bits in santa cruz



-- 
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: "David G. Johnston"
Date:
Subject: Re: [BUGS] BUG #14853: Parameter type is required even when the querydoes not need to know the type
Next
From: balazs@obiserver.hu
Date:
Subject: [BUGS] BUG #14854: daterange[] is an anyarray or anyrange?