From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | pgsql-hackers Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: WIP: cross column correlation ... |
Date: | 2011-02-27 22:17:49 |
Message-ID: | 4D6ACD8D.2080205@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> I think there would be value in giving the DBA an easier way to see
> which tables are hot, but I am really leery about the idea of trying
> to feed that directly into the query planner. I think this is one of
> those cases where we let people tune it manually for starters, and
> then wait for feedback. Eventually someone will say "oh, I never tune
> that by hand any more, ever since I wrote this script which does the
> following computation... and I just run it out cron". And then we
> will get out the party hats. But we will never get the experience we
> need to say what that auto-tuning algorithm will be unless we first
> provide the knob for someone to fiddle with manually.
I'm not disagreeing with that. I'm saying "first, we give DBAs a way to
see which tables are currently hot". Such a feature has multiple
benefits, making it worth the overhead and/or coding effort.
Whether we're shooting for autotuning or manual tuning, it starts with
having the data.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Anton | 2011-02-27 22:31:47 | Fwd: Re: Native XML |
Previous Message | Rémi Zara | 2011-02-27 21:56:28 | Re: pika failing since the per-column collation patch |