| From: | gdr(at)gdr(dot)name |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Cc: | gdr(at)gdr(dot)name |
| Subject: | BUG #14851: Systemd kills long-running recovery |
| Date: | 2017-10-13 09:10:28 |
| Message-ID: | 20171013091028.20254.74268@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | alexey.ermakov | 2017-10-13 11:53:20 | BUG #14852: Refreshing materialized view might lead to a problem "could not access status of transaction" |
| Previous Message | KES | 2017-10-13 08:13:43 | Re: Fwd: [BUGS] BUG #14850: Implement optinal additinal parameter for 'justify' date/time function |