Re: Push down more full joins in postgres_fdw
Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>
From: Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2016-09-14T03:38:10Z
Lists: pgsql-hackers
On Tue, Sep 13, 2016 at 10:28 PM, Robert Haas <robertmhaas@gmail.com> wrote: > On Tue, Sep 6, 2016 at 9:07 AM, Ashutosh Bapat > <ashutosh.bapat@enterprisedb.com> wrote: >> That's not true with the alias information. As long as we detect which >> relations need subqueries, their RTIs are enough to create unique aliases >> e.g. if a relation involves RTIs 1, 2, 3 corresponding subquery can have >> alias r123 without conflicting with any other alias. > > What if RTI 123 is also used in the query? Good catch. I actually meant some combination of 1, 2 and 3, which is unique for a join between r1, r2 and r3. How about r1_2_3 or r1_r2_r3? -- Best Wishes, Ashutosh Bapat EnterpriseDB Corporation The Postgres Database Company
Commits
-
postgres_fdw: Push down FULL JOINs with restriction clauses.
- b30fb56b07a8 10.0 landed