From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
---|---|
To: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: VACUUM always makes all pages dirty |
Date: | 2007-10-24 08:22:01 |
Message-ID: | 471F00A9.3060400@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
ITAGAKI Takahiro wrote:
> VACUUM in 8.3dev always makes all pages dirty even if there are no jobs.
> In 8.2.5, VACUUM produces no dirty pages in the same workload. Therefore,
> VACUUM on 8.3 takes longer time than 8.2. I doubt some bugs in the
> HOT-related codes here, but I cannot point out the actual position yet...
Yeah, it's definitely a HOT-introdued thing. Vacuum calls
heap_page_prune on every page, and this in heap_page_prune is dirtying
the buffer:
> else
> {
> /*
> * If we didn't prune anything, we have nonetheless updated the
> * pd_prune_xid field; treat this as a non-WAL-logged hint.
> */
> SetBufferCommitInfoNeedsSave(buffer);
> }
I don't have time to dig deeper at this moment. I'll take a look later
today, unless someone beats me to it. We obviously don't want to call
SetBufferCommitInfoNeedsSave if we didn't really change the pd_prune_xid
field.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Pavan Deolasee | 2007-10-24 08:45:12 | Re: VACUUM always makes all pages dirty |
Previous Message | Marko Kreen | 2007-10-24 08:04:34 | Re: Feature Freeze date for 8.4 |