To: Simon Riggs <simon@2ndquadrant.com>
cc: Pavan Deolasee <pavan.deolasee@gmail.com>,
	List pgsql-patches <pgsql-patches@postgresql.org>
Subject: Re: [HACKERS] Hint Bits and Write I/O 
In-reply-to: <1216670891.3894.34.camel@ebony.2ndQuadrant> 
References: <1211916951.4489.232.camel@ebony.site>
	<15901.1211931165@sss.pgh.pa.us>
	<1213797209.9468.126.camel@ebony.site>
	<87hcbfq71p.fsf@oxford.xeocode.com>
	<1214578938.3845.423.camel@ebony.site>
	<1214865781.3845.525.camel@ebony.site>
	<2e78013d0807202306t21ff41a9q53673dc9a48bf859@mail.gmail.com>
	<1216670891.3894.34.camel@ebony.2ndQuadrant>
Comments: In-reply-to Simon Riggs <simon@2ndquadrant.com>
	message dated "Mon, 21 Jul 2008 21:08:11 +0100"
Date: Mon, 21 Jul 2008 16:33:55 -0400
Message-ID: <17500.1216672435@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Simon Riggs <simon@2ndquadrant.com> writes:
> On Mon, 2008-07-21 at 11:36 +0530, Pavan Deolasee wrote:
>> I think we should try at least one or two possible optimizations and
>> get some numbers before we jump and make substantial changes to the
>> code.

> You know you're suggesting months of tests and further discussion. :-(

I agree with Pavan that we should have something that'd at least serve
as test scaffolding to verify that the framework patch is sane.  The
test code needn't be anything we'd want to commit.  It seems like
largely the same kind of issue as with your stats-hooks patch.

			regards, tom lane