Re: [HACKERS] path toward faster partition pruning - Mailing list pgsql-hackers

From David Rowley
Subject Re: [HACKERS] path toward faster partition pruning
Date
Msg-id CAKJS1f9+dHias8tPX2JxmY4o3amto3uVeyHNc77i+EGYG8+1Cg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] path toward faster partition pruning  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
List pgsql-hackers
On 9 January 2018 at 21:40, Amit Langote <Langote_Amit_f8@lab.ntt.co.jp> wrote:
> Sorry about the absence in the last few days.  I will post a new version
> addressing various review comments by the end of this week.

One more thing I discovered while troubleshooting a bug Beena reported
in the run-time partition pruning patch is that
classify_partition_bounding_keys properly does;

if (EXPR_MATCHES_PARTKEY(leftop, partattno, partexpr))
    constexpr = rightop;
else if (EXPR_MATCHES_PARTKEY(rightop, partattno, partexpr))
    constexpr = leftop;
else
    /* Clause not meant for this column. */
    continue;

for OpExpr clauses, but does not do the same for leftop for the
ScalarArrayOpExpr test.

-- 
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: [HACKERS] Runtime Partition Pruning
Next
From: Masahiko Sawada
Date:
Subject: Re: [HACKERS] GUC for cleanup indexes threshold.