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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, 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-13 18:52:22
Message-ID: 17873.1197571942@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> Simon Riggs wrote:
>> We might be able to have bgwriter set hint bits on dirty blocks,

> I don't think that works, because the bgwriter has no access to the
> catalogs, therefore it cannot examine the page contents. To bgwriter,
> pages are opaque.

Another issue is that this'd require bgwriter to access the clog SLRU
area. I seem to remember worrying that that could lead to low-level
deadlocks, though I cannot recall the exact case at the moment.
Even without that, it would increase contention for SLRU, which we
probably don't want.

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Campbell, Lance 2007-12-13 19:10:28 Putting files into fields in a table
Previous Message Simon Riggs 2007-12-13 18:12:44 Re: Heavy write activity on first vacuum of fresh TOAST data