From: | John R Pierce <pierce(at)hogranch(dot)com> |
---|---|
To: | gdr(at)gdr(dot)name, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #14851: Systemd kills long-running recovery |
Date: | 2017-10-13 19:03:57 |
Message-ID: | 81d229fd-02f7-13a2-47ab-3bb9435f4c7d@hogranch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 10/13/2017 2:10 AM, gdr(at)gdr(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | balazs | 2017-10-13 19:45:21 | BUG #14854: daterange[] is an anyarray or anyrange? |
Previous Message | David G. Johnston | 2017-10-13 15:38:12 | Re: BUG #14853: Parameter type is required even when the query does not need to know the type |