Re: NOT IN subquery optimization

From: "Li, Zheng" <zhelli(at)amazon(dot)com>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: NOT IN subquery optimization
Date: 2019-06-26 21:26:16
Message-ID: 095FE8E8-4004-4EDC-B7B0-C115F6871EF3@amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

I'm submitting patch v2.2.

This version fixed an issue that involves CTE. Because we call subquery_planner before deciding whether to proceed with the transformation, we need to setup access to upper level CTEs at this point if the subquery contains any CTE RangeTblEntry.

Also added more test cases of NOT IN accessing CTEs, including recursive CTE. It's nice that CTE can use index now!

Let me know if you have any comments.

Regards,
-----------
Zheng Li
AWS, Amazon Aurora PostgreSQL

Attachment Content-Type Size
not_in_to_anti_join_transformation_v2_2.patch application/octet-stream 163.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dent John 2019-06-26 22:17:06 Re: [PATCH] src/test/modules/dummy_index -- way to test reloptions from inside of access method
Previous Message Fabien COELHO 2019-06-26 20:27:28 RE: psql - add SHOW_ALL_RESULTS option