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

Re: [HACKERS] Hint Bits and Write I/O

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: List pgsql-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] Hint Bits and Write I/O
Date: 2008-08-01 23:10:14
Message-ID: 20080801231014.GM4321@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Simon Riggs wrote:

> The first "half" is actually quite large, but that makes it even more
> sensible to commit this part now.
> 
> The enclosed patch introduces the machinery by which we might later
> optimise hint bit setting. It differentiates between hint bit setting
> and block dirtying, when the distinction can safely be made. It acts
> safely during VACUUM and correctly during checkpoint. In all other
> respects it emulates current behaviour.

I think it makes sense to commit this patch now, per previous
discussions on which we have agreed to make incremental changes.  I
think we should just get rid of the bogus changes Pavan identified.

I'm just wondering if the change of usage_count from 16 to 8 bits was
discussed and agreed?

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

pgsql-hackers by date

Next:From: Andrew GierthDate: 2008-08-01 23:35:55
Subject: Re: WITH RECUSIVE patches 0723
Previous:From: Tom LaneDate: 2008-08-01 21:42:41
Subject: Re: Re: [Pljava-dev] Should creating a new base type require superuser status?

pgsql-patches by date

Next:From: Andrew GierthDate: 2008-08-01 23:35:55
Subject: Re: WITH RECUSIVE patches 0723
Previous:From: chrisDate: 2008-08-01 18:02:30
Subject: Re: pg_dump additional options for performance

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