Re: [PATCH] Patch to compute Max LSN of Data Pages - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: [PATCH] Patch to compute Max LSN of Data Pages
Date
Msg-id 009f01cdc2ef$45c51a90$d14f4fb0$@kapila@huawei.com
Whole thread Raw
In response to Re: [PATCH] Patch to compute Max LSN of Data Pages  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
On Wednesday, November 14, 2012 10:19 PM Fujii Masao wrote:
> On Thu, Nov 15, 2012 at 12:55 AM, Amit Kapila <amit.kapila@huawei.com>
> wrote:
> > Now user can use this utility to decide if new-standby has max LSN
> greater
> 
> > And that situation can occur when new-standby has startpoint LSN
> greater
> > than new-master?
> 
> Whether the backup is required has nothing to do with the startpoint.
> The backup is required when the data page in old-master precedes
> the last applied LSN in old-standby (i.e., new-master) at the moment
> of the failover. Without the backup, there is no way to revert the data
> which is ahead of new-master.

Okay. 
So as Robert and Alvaro suggested to have it separate utility rather than
having options in pg_resetxlog to print MAX LSN seems to be quite
appropriate.
I am planning to update the patch to make it a separate utility as
pg_computemaxlsn with options same as what I have proposed for pg_resetxlog
to print MAX LSN.
So considering it a separate utility there can be 2 options:
a. have a utility in contrib.
b. have a utility in bin similar to pg_resetxlog.
What is the best place to have it?

With Regards,
Amit Kapila.




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Doc patch, put commas in the right place in pg_restore docs
Next
From: Shigeru Hanada
Date:
Subject: Re: Move postgresql_fdw_validator into dblink