Re: [HACKERS] recover corrupted pg_controldata from WAL

2005-07-22 Thread yuanjia lee
Hi Tom I agree that it is wrong to use the information from the file name itself. I will try to read the xlp_pageaddr out from the segment header to figure out which one is the lastest one. In the mutilple time lines scenario, if the pg_control file crashed, and the current time line information

Re: [HACKERS] recover corrupted pg_controldata from WAL

2005-07-21 Thread Tom Lane
yuanjia lee <[EMAIL PROTECTED]> writes: > The algorithm of searching the WAL is like this: > 1. Read name of the segment files from xlog directory, and put all of > their name into an one way list, the list is descending according to the time > line, xlog id, segement id. (Athough I use onl

Re: [HACKERS] recover corrupted pg_controldata from WAL

2005-07-21 Thread Brusser, Michael
should be.   Perhaps at the minimum the –help option could be extended? Thank you, Mike   From: yuanjia lee [mailto:[EMAIL PROTECTED] Sent: Thursday, July 21, 2005 7:09 AM To: pgsql-hackers@postgresql.org Subject: [HACKERS] recover corrupted pg_controldata from WAL   Hi, All   I am

[HACKERS] recover corrupted pg_controldata from WAL

2005-07-21 Thread yuanjia lee
Hi, All   I am preparing to enhance the pg_resetlog to support recover corrupted pg_control data from WAL. I had finised the code now and testing it, but before I bring it out for patch review, I want to discuss some issues here to get some advice.   The functionality of reset the xlog is the same