| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila(at)huawei(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Cédric Villemain <cedric(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: Allow WAL information to recover corrupted pg_controldata |
| Date: | 2012-06-19 14:14:13 |
| Message-ID: | CAHGQGwHFU6c+dKU=UFZNChai1xg35dkqbcfji269AYVczXYHZg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 19, 2012 at 2:44 AM, Amit Kapila <amit(dot)kapila(at)huawei(dot)com> wrote:
>> AFAIR you can create pg_control from scratch already with pg_resetxlog.
>> The hard part is coming up with values for the counters, such as the
>> next WAL location. Some of them such as next OID are pretty harmless
>> if you don't guess right, but I'm worried that wrong next WAL could
>> make things worse not better.
>
> I believe if WAL files are proper as mentioned in Alvaro's mail, the purposed logic should generate
> correct values.
> Do you see any problem in logic purposed in my original mail.
> Can I resume my work on this feature?
Maybe I'm missing your point, but... why don't you just use PITR to
recover from the corruption of pg_control?
Regards,
--
Fujii Masao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-06-19 14:17:01 | Re: [PATCH 10/16] Introduce the concept that wal has a 'origin' node |
| Previous Message | Merlin Moncure | 2012-06-19 13:49:12 | Re: pgsql_fdw in contrib |