From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: getting rid of freezing |
Date: | 2013-06-01 17:56:34 |
Message-ID: | CA+U5nM+KroxQOggRm7Mv3sap-ZG4Zr_G1yT5r8h-C2jq8Ecu7g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 28 May 2013 15:15, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Sat, May 25, 2013 at 6:14 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> I think the right way is actually to rethink and simplify all this
>> complexity of Freezing/Pruning/Hinting/Visibility
>
> I agree, but I think that's likely to have to wait until we get a
> pluggable storage API, and then a few years beyond that for someone to
> develop the technology to enable the new and better way. In the
> meantime, if we can eliminate or even reduce the impact of freezing in
> the near term, I think that's worth doing.
I think we can do better more quickly than that.
Andres' basic idea of skipping freeze completely was a valuable one
and is the right way forwards. And it looks like the epoch based
approach that Heikki and I have come up seems likely to end up
somewhere workable.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2013-06-01 18:11:06 | Re: detecting binary backup in progress |
Previous Message | Simon Riggs | 2013-06-01 17:49:43 | Re: Vacuum, Freeze and Analyze: the big picture |