From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: hint bit cache v5 |
Date: | 2011-05-10 17:32:25 |
Message-ID: | BANLkTimBRzLL66NN7G7Pu9d6P6vzS6Y6XQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, May 10, 2011 at 11:59 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On Mon, May 9, 2011 at 5:12 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
>
>> I'd like to know if this is a strategy that merits further work...If
>> anybody has time/interest that is. It's getting close to the point
>> where I can just post it to the commit fest for review. In
>> particular, I'm concerned if Tom's earlier objections can be
>> satisfied. If not, it's back to the drawing board...
>
> I'm interested in what you're doing here.
>
> From here, there's quite a lot of tuning possibilities. It would be
> very useful to be able to define some metrics we are interested in
> reducing and working out how to measure them.
>
> That way we can compare all the different variants of this to see
> which way of doing things works best.
thanks for that! I settled on this approach because the downside
cases should hopefully be pretty limited. The upside is a matter of
debate although fairly trivial to demonstrate synthetically.
I'm looking for some way of benchmarking the benefits in non-simulated
fashion. We desperately need something like a performance farm (as
many many others have mentioned).
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | J. Greg Davidson | 2011-05-10 17:32:47 | Re: 4.1beta1: ANYARRAY disallowed for DOMAIN types which happen to be arrays |
Previous Message | Kevin Grittner | 2011-05-10 17:25:34 | Re: the big picture for index-only scans |