Re: Reduce maximum error in tuples estimation after vacuum.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila(at)huawei(dot)com>
Cc: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Reduce maximum error in tuples estimation after vacuum.
Date: 2013-06-27 15:39:43
Message-ID: CA+Tgmobii50TnqUyaqJ2hhyP6eWCKth_Kq39KvuSkj=RzeDkZg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jun 27, 2013 at 7:27 AM, Amit Kapila <amit(dot)kapila(at)huawei(dot)com> wrote:
> Now I can look into it further, I have still not gone through in detail
> about your new approach to calculate the reltuples, but I am wondering
> whether there can be anyway with which estimates can be improved with
> different calculation in vac_estimate_reltuples().

I think this is getting at the threshold question for this patch,
which is whether it's really making things better or just moving the
problems around. I mean, I have no problem accepting that the new
algorithm is (1) reasonably cheap and (2) better in some cases. But
if it's worse in other cases, which AFAICS hasn't been discussed, then
it's no good.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2013-06-27 15:44:28 Re: MD5 aggregate
Previous Message Peter Eisentraut 2013-06-27 15:35:12 Re: Add more regression tests for dbcommands