Re: VACUUM always makes all pages dirty

From: "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com>
To: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>
Cc: "ITAGAKI Takahiro" <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: VACUUM always makes all pages dirty
Date: 2007-10-24 10:02:06
Message-ID: 2e78013d0710240302gcbcd535i19a1b716f2b9ab09@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10/24/07, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> wrote:
>
>
>
> I am looking at it. We must not call SetBufferCommitInfoNeedsSave unless
> we make any state changes to the page.
>
>
>

The attached patch should fix this. We mark the buffer dirty only if there
is any state change in the page header.

Thanks,
Pavan

--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com

Attachment Content-Type Size
vacuum-dirty-fix.patch text/x-patch 2.2 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2007-10-24 10:23:18 Re: Feature Freeze date for 8.4
Previous Message Dharmendra Goyal 2007-10-24 09:39:11 second DML operation fails with updatable cursor