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

From Fabrízio de Royes Mello
Subject Re: [BUGS] BUG #14851: Systemd kills long-running recovery
Date
Msg-id CAFcNs+qu2Xs3WzA6oWB2A3VxFfJn_gkpcO5ro1k2xmev2f4beg@mail.gmail.com
Whole thread Raw
In response to [BUGS] BUG #14851: Systemd kills long-running recovery  (gdr@gdr.name)
List pgsql-bugs


On Fri, Oct 13, 2017 at 6:10 AM, <gdr@gdr.name> wrote:
>
> 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.
>

Hi,

I don't think here is the best place to report this issue. Try report it to the RPM Build maintainers [1].

Regards,

pgsql-bugs by date:

Previous
From: edpeur@gmail.com
Date:
Subject: [BUGS] BUG #14853: Parameter type is required even when the query does notneed to know the type
Next
From: "David G. Johnston"
Date:
Subject: Re: [BUGS] BUG #14853: Parameter type is required even when the querydoes not need to know the type