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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, List pgsql-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] Hint Bits and Write I/O
Date: 2008-07-21 20:33:55
Message-ID: 17500.1216672435@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Simon Riggs <simon(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2008-07-21 20:37:45 Re: Do we really want to migrate plproxy and citext into PG core distribution?
Previous Message Andrew Sullivan 2008-07-21 20:28:19 Re: Do we really want to migrate plproxy and citext into PG core distribution?

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2008-07-21 20:38:57 Re: pg_dump additional options for performance
Previous Message Tom Lane 2008-07-21 20:16:13 Re: page macros cleanup (ver 04)