From: | "Li, Zheng" <zhelli(at)amazon(dot)com> |
---|---|
To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [UNVERIFIED SENDER] Re: NOT IN subquery optimization |
Date: | 2019-06-14 21:41:06 |
Message-ID: | 812F84BC-702F-4063-95CC-A7DBD7C9D66B@amazon.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Rebased patch is attached.
Comments are welcome.
-----------
Zheng Li
AWS, Amazon Aurora PostgreSQL
On 6/14/19, 5:39 PM, "zhengli" <zhelli(at)amazon(dot)com> wrote:
In our patch, we only proceed with the ANTI JOIN transformation if
subplan_is_hashable(subplan) is
false, it requires the subquery to be planned at this point.
To avoid planning the subquery again later on, I want to keep a pointer of
the subplan in SubLink so that we can directly reuse the subplan when
needed. However, this change breaks initdb for some reason and I'm trying to
figure it out.
I'll send the rebased patch in the following email since it's been a while.
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html
Attachment | Content-Type | Size |
---|---|---|
not_in_to_anti_join_transformation_v2.patch | application/octet-stream | 137.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2019-06-14 22:09:40 | Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS) |
Previous Message | zhengli | 2019-06-14 21:38:24 | Re: NOT IN subquery optimization |