Re: Simplifying the interface of UpdateMinRecoveryPoint - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Simplifying the interface of UpdateMinRecoveryPoint
Date
Msg-id CAB7nPqQg=KYYWzE9XGN3dnRscoUfX5_LLzqBsm3yia2+Lh+fog@mail.gmail.com
Whole thread Raw
In response to Re: Simplifying the interface of UpdateMinRecoveryPoint  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
On Wed, Jul 13, 2016 at 10:31 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
> On 12 July 2016 at 23:49, Michael Paquier <michael.paquier@gmail.com> wrote:
>> Hence why not simplifying its interface and remove the force flag?
>
> Is this change needed as part of a feature? If not, I see no reason for
> change.
>
> If we all work towards meaningful features the code can be cleaned up as we
> go.

That's just refactoring. The interactions between the two arguments of
this routine is plain.
-- 
Michael



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: rethinking dense_alloc (HashJoin) as a memory context
Next
From: Andres Freund
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold <