Re: Re: [COMMITTERS] pgsql: Ensure age() returns a stable value rather than the latest value - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: [COMMITTERS] pgsql: Ensure age() returns a stable value rather than the latest value
Date
Msg-id 16784.1338318002@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Ensure age() returns a stable value rather than the latest value  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> On mån, 2012-05-14 at 15:11 -0400, Tom Lane wrote:
>> (In any case, my primary beef at the moment is not with whether it's a
>> good idea to change age()'s behavior going forward, but rather with
>> having back-patched such a change.)

> Certainly we should leave it alone there.

With back-branch update releases due to be made this week, we need to
decide what if anything we're going to do about changing this.
I have no particular complaint with what Simon's done in HEAD, but
back-patching it was not wise IMO.  I think we should just revert the
patches in the back branches and go back to the way it was before
(complete with failures on slave servers).
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Foreground vacuum and buffer access strategy
Next
From: Heikki Linnakangas
Date:
Subject: GiST buffering build, bug in levelStep calculation