From: | Emre Hasegeli <emre(at)hasegeli(dot)com> |
---|---|
To: | Oleksii Kliukin <alexk(at)hintbits(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: rows estimate in explain analyze for the BRIN index |
Date: | 2015-12-30 17:38:56 |
Message-ID: | CAE2gYzwT0uEWitsOBBM4cM9cx_f8GBxPdH47YapCtGHyn0APSQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> which is much closer to the actual number of rows removed by the index
> recheck + the one left.
Is it better to be closer? We are saying those are the "actual"
values not the estimates. If we cannot provide the actual rows, I
think it is better to provide nothing. Something closer to the
reality would create more confusion. Maybe, we just just return the
number of blocks, and put somewhere a note about it. The actual row
count is already available on the upper part of the plan.
By the way, the estimation is a bigger problem than that. Please see
my patch [1] about it.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-12-30 17:41:56 | Re: Some 9.5beta2 backend processes not terminating properly? |
Previous Message | Shay Rojansky | 2015-12-30 17:38:23 | Re: Some 9.5beta2 backend processes not terminating properly? |