From: | Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com> |
---|---|
To: | gdr(at)gdr(dot)name |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #14851: Systemd kills long-running recovery |
Date: | 2017-10-13 15:23:52 |
Message-ID: | CAFcNs+qu2Xs3WzA6oWB2A3VxFfJn_gkpcO5ro1k2xmev2f4beg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Fri, Oct 13, 2017 at 6:10 AM, <gdr(at)gdr(dot)name> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference: 14851
> Logged by: GDR !
> Email address: gdr(at)gdr(dot)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,
[1] https://yum.postgresql.org/contact.php
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog: http://fabriziomello.github.io
>> Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
>> Github: http://github.com/fabriziomello
From | Date | Subject | |
---|---|---|---|
Next 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 |
Previous Message | edpeur | 2017-10-13 14:03:50 | BUG #14853: Parameter type is required even when the query does not need to know the type |