On Tue, Jul 31, 2012 at 8:09 AM, Amit kapila <amit.kap...@huawei.com> wrote: >>> Based on the discussion and suggestions in this mail chain, following >>> features can be implemented: >>> >>> 1. To compute the value of max LSN in data pages based on user input >>> whether he wants it for an individual > >>> file, a particular directory or whole database. >>> >>> 2a. To search the available WAL files for the latest checkpoint record >>> and prints the value. >>> 2b. To search the available WAL files for the latest checkpoint record >>> and recreates a pg_control file pointing at > >>> that checkpoint. > >>> I have kept both options to address different kind of corruption >>> scenarios. > >> I think I can see all of those things being potentially useful. There >> are a couple of pending patches that will revise the WAL format >> slightly; not sure how much those are likely to interfere with any >> development you might do on (2) in the meantime. > > Based on above conclusion, I have prepared a patch which implements Option-1
I wonder if we shouldn't make this a separate utility, rather than something that is part of pg_resetxlog. Anyone have a thought on that topic? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
