Re: Heavy write activity on first vacuum of fresh TOAST data

From: Russell Smith <mr-russ(at)pws(dot)com(dot)au>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Heavy write activity on first vacuum of fresh TOAST data
Date: 2007-12-14 07:30:11
Message-ID: 47623103.7030700@pws.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Simon Riggs wrote:
> On Thu, 2007-12-13 at 15:19 -0600, Kevin Grittner wrote:
>
>> What impact would lack of the hint bits have until a vacuum?
>>
>
> Vacuum isn't important here. Its the first idiot to read the data that
> gets hit.
>
>
Given vacuum must then touch every page, is there a win in only setting
hint bits on pages where vacuum has to do some other work on the page?
As vacuum is causing significant IO load for data that may not be
accessed for some time.

The question becomes what is the impact of not setting hint bits? Is it
better or worse than the IO caused by vacuum?

Regards

Russell Smith

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2007-12-14 07:42:42 Re: Heavy write activity on first vacuum of fresh TOAST data
Previous Message Kevin Grittner 2007-12-13 23:43:27 Re: Heavy write activity on first vacuum of fresh TOAST data