Re: Allow WAL information to recover corrupted pg_controldata
От | Fujii Masao |
---|---|
Тема | Re: Allow WAL information to recover corrupted pg_controldata |
Дата | |
Msg-id | CAHGQGwHFU6c+dKU=UFZNChai1xg35dkqbcfji269AYVczXYHZg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Allow WAL information to recover corrupted pg_controldata (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: Allow WAL information to recover corrupted pg_controldata
|
Список | pgsql-hackers |
On Tue, Jun 19, 2012 at 2:44 AM, Amit Kapila <amit.kapila@huawei.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
В списке pgsql-hackers по дате отправления: