| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: hint bit cache v5 |
| Date: | 2011-05-10 16:59:25 |
| Message-ID: | BANLkTik-LB+7XRTH85SdA0xk9N_LdMzbuw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-05-10 17:00:11 | Re: crash-safe visibility map, take five |
| Previous Message | Simon Riggs | 2011-05-10 16:57:19 | Re: collateral benefits of a crash-safe visibility map |