Re: [HACKERS] TPC-H Q20 from 1 hour to 19 hours! - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: [HACKERS] TPC-H Q20 from 1 hour to 19 hours!
Date
Msg-id CAH2-Wz=zPeLz4LPwWxyLTD=4T91Jeo088aP2y7pgMu2u8xtRBQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] TPC-H Q20 from 1 hour to 19 hours!  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] TPC-H Q20 from 1 hour to 19 hours!  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
List pgsql-hackers
On Sun, Jun 11, 2017 at 10:36 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Do you mean teaching the optimizer to do something like this?:
>
> Uh, no.  I don't think we want to add any run-time checks.  The point in
> this example is that we'd get a better rowcount estimate if we noticed
> that the FK constraint could be considered while estimating the size of
> the partsupp-to-aggregated-subquery join.

Sorry for not considering the context of the thread more carefully.
Robert said something about selectivity estimation and TPC-H to me,
which I decide to research; I then rediscovered this thread.

Clearly Q20 is designed to reward systems that do better with moving
predicates into subqueries, as opposed to systems with better
selectivity estimation.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] TPC-H Q20 from 1 hour to 19 hours!
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] PostgreSQL 10 changes in exclusion constraints - did something change? CASE WHEN behavior oddity