| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Freezing without write I/O |
| Date: | 2013-06-01 20:26:20 |
| Message-ID: | CA+TgmoamfbEUfnSO_71Y1JAQfKgU007xxD=hmjGew=CYLq-miw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Jun 1, 2013 at 3:22 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> If we set a bit, surely we need to write the page. Isn't that what we
> were trying to avoid?
No, the bit only gets set in situations when we were going to dirty
the page for some other reason anyway. Specifically, if a page
modification discovers that we've switched epochs (but just once) and
the bit isn't already set, we can set it in lieu of scanning the
entire page for tuples that need freezing.
Under this proposal, pages that don't contain any dead tuples needn't
be dirtied for freezing, ever. Smells like awesome.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2013-06-01 20:27:35 | Re: Optimising Foreign Key checks |
| Previous Message | Robert Haas | 2013-06-01 20:21:36 | Re: Freezing without write I/O |