I have uploaded the patch for new option in pg_resetxlog at below location:
https://commitfest.postgresql.org/action/patch_view?id=897
This completes the implementation of Option-2 discussed in below mail.
Now I will work on Option-1 (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.)
> From: Amit kapila
> Sent: Wednesday, July 18, 2012 7:17 PM
> Patch implementing the design in below mail chain is attached with this mail.
>From: Amit Kapila [mailto:amit.kapila@huawei.com]
>Sent: Thursday, July 05, 2012 10:21 AM
>>From: Robert Haas [mailto:robertmhaas@gmail.com]
>>Sent: Friday, June 22, 2012 8:59 PM
>>On Fri, Jun 22, 2012 at 5:25 AM, Amit Kapila <amit.kapila@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.
With Regards,
Amit Kapila.