From: | Amit Kapila <amit(dot)kapila(at)huawei(dot)com> |
---|---|
To: | "'Aidan Van Dyk'" <aidan(at)highrise(dot)ca> |
Cc: | "'Pg Hackers'" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Allow WAL information to recover corrupted pg_controldata |
Date: | 2012-06-21 03:32:02 |
Message-ID: | 003101cd4f5e$6cb4f0d0$461ed270$@kapila@huawei.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Just so I understand correctly, the aim of this is to "fix" the
> situation where out of the thousands of files and 100s of GB of data
> in my pg directory, the *only* corruption is that a single file
> pg_control file is missing?
This is just an example I have used to explain what should be the best way to generate
Next-LSN.
The overall aim for this feature is to start the database with as much accuracy as possible after database corruption occurred due to missing files or hardware crash.
However it is not possible to start with full consistency and accuracy after such a
Situation.
-----Original Message-----
From: Aidan Van Dyk [mailto:aidan(at)highrise(dot)ca]
Sent: Wednesday, June 20, 2012 7:13 PM
To: Amit Kapila
Cc: Pg Hackers
Subject: Re: [HACKERS] Allow WAL information to recover corrupted pg_controldata
On Wed, Jun 20, 2012 at 9:21 AM, Amit Kapila <amit(dot)kapila(at)huawei(dot)com> wrote:
> Example Scenario -
> Now assume we have Data files and WAL files intact and only control file is lost.
Just so I understand correctly, the aim of this is to "fix" the
situation where out of the thousands of files and 100s of GB of data
in my pg directory, the *only* corruption is that a single file
pg_control file is missing?
a.
--
Aidan Van Dyk Create like a god,
aidan(at)highrise(dot)ca command like a king,
http://www.highrise.ca/ work like a slave.
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2012-06-21 04:57:20 | Re: Backport of fsync queue compaction |
Previous Message | Amit Kapila | 2012-06-21 03:24:45 | Re: Allow WAL information to recover corrupted pg_controldata |