| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Brian Faherty <anothergenericuser(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Missing pg_control crashes postmaster |
| Date: | 2018-07-25 15:33:47 |
| Message-ID: | d9af6065-0ae0-832a-b964-00deff34baf4@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 7/25/18 11:26 AM, Andres Freund wrote:
> On 2018-07-25 11:19:49 -0400, David Steele wrote:
>
> If one wanted to improve recoverability in scenarios like this, there'd
> be actually useful things like adding the option to extract control
> files, FPIs, clog contents from the WAL with pg_waldump.
I think you'd need to be a bit careful about what to trust in the WAL
but presumably the last checkpoint LSN would be safe enough.
At the end of the day good backups are the best protection against an
issue like this.
Regards,
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2018-07-25 15:38:25 | Re: Missing pg_control crashes postmaster |
| Previous Message | Tom Lane | 2018-07-25 15:33:14 | Re: Missing pg_control crashes postmaster |