| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Deferring transaction wraparound |
| Date: | 2013-06-02 10:39:42 |
| Message-ID: | CA+U5nMJ3koWBpm2QBu4DLLuM97yPY=ghqcBDg1tQ0-MFM6U5oQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1 June 2013 09:22, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> A much better idea is to hold the xmin epoch on the tuple, in addition
> to the xid, if there was a good place to hold this.
This idea is an almost exact duplicate of Heikki Linnakangas' idea for
exactly the same problem.
Given Robert Haas' idea to use the page LSN to indicate the epoch last
changes were made, it allows us to do pretty much this idea in a
slightly easier way.
So this idea withdrawn as a proposal, assuming we can go ahead with
the above mentioned approach.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cédric Villemain | 2013-06-02 10:56:25 | Re: PostgreSQL 9.3 beta breaks some extensions "make install" |
| Previous Message | Simon Riggs | 2013-06-02 09:45:21 | Re: Optimising Foreign Key checks |