aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/postgres_fdw.h
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2016-04-20 23:34:07 -0400
committerRobert Haas <rhaas@postgresql.org>2016-04-20 23:54:19 -0400
commit5b1f9ce1d9e8dcae2bcd93b2becffaba5e4f3049 (patch)
treeaf17513006e12e0225dc30d07d1668c78cdd2966 /contrib/postgres_fdw/postgres_fdw.h
parentcbabb70f35bb0e5bac84b9f15ecadc82868ad9f9 (diff)
downloadpostgresql-5b1f9ce1d9e8dcae2bcd93b2becffaba5e4f3049.tar.gz
postgresql-5b1f9ce1d9e8dcae2bcd93b2becffaba5e4f3049.zip
postgres_fdw: Don't push down certain full joins.
If there's a filter condition on either side of a full outer join, it is neither correct to attach it to the join's ON clause nor to throw it into the toplevel WHERE clause. Just don't push down the join in that case. To maximize the number of cases where we can still push down full joins, push inner join conditions into the ON clause at the first opportunity rather than postponing them to the top-level WHERE clause. This produces nicer SQL, anyway. This bug was introduced in e4106b2528727c4b48639c0e12bf2f70a766b910. Ashutosh Bapat, per report from Rajkumar Raghuwanshi.
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.h')
0 files changed, 0 insertions, 0 deletions