On Wed, Oct 26, 2016 at 1:40 PM, Amit Kapila <amit.kapil...@gmail.com> wrote:
> If you are inclined towards this solution, then I think what we need
> to do is to change the API UpdateMinRecoveryPoint() such that it's
> second parameter can take three values.  0 means update
> minRecoveryPoint to passed lsn if minRecoveryPoint < lsn; 1 means
> update minRecoveryPoint to latest replayed point if minRecoveryPoint <
> lsn, same as currently false for *force*; 2 indicates same behaviour
> as current *force* as true.  Also we need to pass currentTLI parameter
> (lastCheckPoint.ThisTimeLineID) to this API to update
> minRecoveryPointTLI.  I have not tried this, but I think something on
> these lines should work.

0 is the behavior that you get when force = false, so it works as 1, no?

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to