Re: [HACKERS] Slow count(*) again...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Mladen Gogala <mladen(dot)gogala(at)vmsinfo(dot)com>, Greg Smith <greg(at)2ndquadrant(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, "david(at)lang(dot)hm" <david(at)lang(dot)hm>, Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, Vitalii Tymchyshyn <tivv00(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: [HACKERS] Slow count(*) again...
Date: 2011-02-03 17:46:48
Message-ID: 25146.1296755208@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> I don't, however, agree with his contention that this is easy to
> implement. It would be easy to implement something that sucked. It
> would be hard to implement something that actually helped in the cases
> where the existing settings aren't already sufficient.

Exactly. A hint system that actually did more good than harm would be a
very nontrivial project. IMO such effort is better spent on making the
optimizer smarter.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2011-02-03 17:50:08 Re: ALTER EXTENSION UPGRADE, v3
Previous Message Chris Browne 2011-02-03 17:44:23 Re: [HACKERS] Slow count(*) again...

Browse pgsql-performance by date

  From Date Subject
Next Message Robert Haas 2011-02-03 17:52:34 Re: Exhaustive list of what takes what locks
Previous Message Chris Browne 2011-02-03 17:44:23 Re: [HACKERS] Slow count(*) again...