| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Brian Faherty <anothergenericuser(at)gmail(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Missing pg_control crashes postmaster |
| Date: | 2018-07-23 19:49:33 |
| Message-ID: | CAKFQuwaddW5vijF9rNhuvwEub08QnEzWft8hKbA=4jeKCq=F8w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jul 23, 2018 at 12:31 PM, Brian Faherty <
anothergenericuser(at)gmail(dot)com> wrote:
> There does not really seem to be a need for this behavior as all the
> information postgres needs is in memory at this point. I propose with
> a patch to just recreate pg_control on updates if it does not exist.
Or at minimum create said file with a different name in PGDATA so an admin
can rename it should they wish to accept the in memory version as being a
valid replacement for whatever ended up happening to the original.
Even if it can be safely rebuilt having pg_control removed out from under a
running server seems like something that shouldn't happen and the server is
in its rights to panic if it does.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-07-23 19:55:48 | Re: Missing pg_control crashes postmaster |
| Previous Message | Brian Faherty | 2018-07-23 19:31:13 | Missing pg_control crashes postmaster |