| From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Tatsuo Ishii <ishii(at)postgresql(dot)org>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: multivariate statistics v14 |
| Date: | 2016-03-22 09:23:23 |
| Message-ID: | df28c9e7-cb66-02b8-b497-d979e4dabf4f@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 03/22/2016 06:53 AM, Jeff Janes wrote:
> On Sun, Mar 20, 2016 at 4:34 PM, Tomas Vondra
> <tomas(dot)vondra(at)2ndquadrant(dot)com> wrote:
>>
>>
>> D'oh. Thanks for reporting. Attached is v16, hopefully fixing the few
>> remaining whitespace issues.
>
> Hi Tomas,
>
> I'm trying out v16 against a common problem, where postgresql thinks
> it is likely top stop early during a "order by (index express) limit
> 1" but it doesn't actually stop early due to cross-column
> correlations. But the multivariate statistics don't seem to help. Am
> I doing this wrong, or just expecting too much?
Yes, I think you're expecting a too much from the current patch.
I've been thinking about perhaps addressing cases like this in the
future, but it requires tracking position within the table somehow (e.g.
by means of including ctid in the table, or something like that), and
the current patch does not implement that.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yury Zhuravlev | 2016-03-22 09:41:43 | NOT EXIST for PREPARE |
| Previous Message | Andres Freund | 2016-03-22 09:18:52 | Re: checkpointer continuous flushing |