Re: NOT IN subquery optimization - Mailing list pgsql-hackers

From Li, Zheng
Subject Re: NOT IN subquery optimization
Date
Msg-id 095FE8E8-4004-4EDC-B7B0-C115F6871EF3@amazon.com
Whole thread Raw
In response to Re: NOT IN subquery optimization  ("Li, Zheng" <zhelli@amazon.com>)
Responses Re: NOT IN subquery optimization
List 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
thetransformation, 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

pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: RE: psql - add SHOW_ALL_RESULTS option
Next
From: Dent John
Date:
Subject: Re: [PATCH] src/test/modules/dummy_index -- way to test reloptionsfrom inside of access method