From: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
---|---|
To: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Use extended statistics to estimate (Var op Var) clauses |
Date: | 2021-06-13 20:28:43 |
Message-ID: | e0890e8a-c524-6702-f9ad-a16f9490bcf7@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
Here is a slightly updated version of the patch - rebased to current
master and fixing some minor issues to handle expressions (and not just
the Var nodes as before).
The changes needed to support (Expr op Expr) are mostly mechanical,
though I'm sure the code needs some cleanup. The main issue I ran into
is the special case clauselist_selectivity, which does
if (list_length(clauses) == 1)
return clause_selectivity_ext(...);
which applies to cases like "WHERE a < b" which can now be handled by
extended statistics, thanks to this patch. But clause_selectivity_ext
only used to call restriction_selectivity for these clauses, which does
not use extended statistics, of course.
I considered either getting rid of the special case, passing everything
through extended stats, including cases with a single clause. But that
ends up affecting e.g. OR clauses, so I tweaked clause_selectivity_ext a
bit, which seems like a better approach.
regards
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Attachment | Content-Type | Size |
---|---|---|
0001-Handling-Expr-op-Expr-clauses-in-extended-s-20210613.patch | text/x-patch | 24.9 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-06-13 20:48:48 | Re: Continuing instability in insert-conflict-specconflict test |
Previous Message | Jonathan S. Katz | 2021-06-13 18:46:36 | Re: unnesting multirange data types |