| From: | GDR! <gdr(at)gdr(dot)name> |
|---|---|
| To: | John R Pierce <pierce(at)hogranch(dot)com>,pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #14851: Systemd kills long-running recovery |
| Date: | 2017-10-14 04:56:36 |
| Message-ID: | 4DD668DD-2A38-42DD-9D3D-C8BFC99B39E1@gdr.name |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On October 13, 2017 9:03:57 PM GMT+02:00, John R Pierce <pierce(at)hogranch(dot)com> wrote:
>
>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,
As Fabrizio suggested, I have created a bug report at the packaging redmine:
https://redmine.postgresql.org/issues/2786
I'm not following Postgres bugs and I'm only an user since 9.4 so my experience is moderate, but I've not yet encountered a scenario where automatically killing a database server is desirable when it's slow to start up. Do you have some scenario in mind where you'd like systemd to kill a server but only when it's not in recovery?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-10-14 10:46:12 | Re: BUG #14849: jsonb_build_object doesn't like VARIADIC calls very much |
| Previous Message | Tom Lane | 2017-10-13 22:28:15 | Re: BUG #14854: daterange[] is an anyarray or anyrange? |