From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Setting vacuum_freeze_min_age really low |
Date: | 2013-05-13 17:21:54 |
Message-ID: | CA+TgmobGz+PUrG4KqZ1wt84+Q1RvCbDUi-gL_AbF0VYWPtUFDg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Sun, May 12, 2013 at 8:50 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> [ a response that I entirely agree with ]
+1 to all that.
It's maybe worth noting that it's probably fairly uncommon for vacuum
to read a page and not dirty it, because if the page is all-visible,
we won't read it. And if it's not all-visible, and there's nothing
else interesting to do with it, we'll probably make it all-visible,
which will dirty it. It can happen, if for example we vacuum a page
with no dead tuples while the inserting transaction is still running,
or committed but not yet all-visible. Of course, in those cases we
won't be able to freeze, either.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2013-05-13 17:43:22 | Re: Setting vacuum_freeze_min_age really low |
Previous Message | ach | 2013-05-13 15:01:33 | statistics target for columns in unique constraint? |