Skip site navigation (1) Skip section navigation (2)

Re: pgsql: Update item description: * Considerhaving the background writer

From: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Bruce Momjian <momjian(at)postgresql(dot)org>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Update item description: * Considerhaving the background writer
Date: 2007-12-17 22:46:10
Message-ID: 4766FC32.8090403@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-committers
Simon Riggs wrote:
> On Mon, 2007-12-17 at 01:40 +0000, Bruce Momjian wrote:
>> Log Message:
>> -----------
>> Update item description:
>>
>> * Consider having the background writer update the transaction status
>>   hint bits before writing out the page
>>
>>   Implementing this requires the background writer to have access to system
>>   catalogs and the transaction status log.
> 
> Not very sure why you've added this one to the TODO list?
> 
> I raised it as not-a-good idea and I think Tom and Alvaro agreed. i.e. I
> mentioned it in order to kill it. It's a ton of work for what very well
> might be overhead rather than gain.

I actually do feel it might be valuable. All our opinions are based on 
gut-feeling, though, so would need benchmarking to see if it's really 
worth it or not.

I think we could get away without accessing system catalogs in bgwriter, 
if we flagged heap pages as such in ReadBuffer. Just a thought..

-- 
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com

In response to

Responses

pgsql-committers by date

Next:From: Simon RiggsDate: 2007-12-17 23:24:16
Subject: Re: pgsql: Update item description: * Considerhavingthe background writer
Previous:From: Simon RiggsDate: 2007-12-17 22:28:33
Subject: Re: pgsql: Update item description: * Considerhaving the background writer

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group