Tom Lane 8b6294c7a5 Change more places to be less trusting of RestrictInfo.is_pushed_down. ... On further reflection, commit e5d83995e didn't go far enough: pretty much everywhere in the planner that examines a clause's is_pushed_down flag ought to be changed to use the more complicated behavior where we also check the clause's required_relids. Otherwise we could make incorrect decisions about whether, say, a clause is safe to use as a hash clause. Some (many?) of these places are safe as-is, either because they are never reached while considering a parameterized path, or because there are additional checks that would reject a pushed-down clause anyway. However, it seems smarter to just code them all the same way rather than rely on easily-broken reasoning of that sort. In support of that, invent a new macro RINFO_IS_PUSHED_DOWN that should be used in place of direct tests on the is_pushed_down flag. Like the previous patch, back-patch to all supported branches. Discussion: https://postgr.es/m/f8128b11-c5bf-3539-48cd-234178b2314d@proxel.se		2018-04-20 15:19:16 -04:00
..
expected	Fix test case for 'outer pathkeys do not match mergeclauses' fix.	2018-01-30 14:47:02 -05:00
sql	Fix test case for 'outer pathkeys do not match mergeclauses' fix.	2018-01-30 14:47:02 -05:00
.gitignore
connection.c	Re-establish postgres_fdw connections after server or user mapping changes.	2017-07-21 12:51:38 -04:00
deparse.c	Fix postgres_fdw to cope with duplicate GROUP BY entries.	2018-01-12 16:52:49 -05:00
Makefile	Allow postgres_fdw to ship extension funcs/operators for remote execution.	2015-11-03 18:42:18 -05:00
option.c	Phase 3 of pgindent updates.	2017-06-21 15:35:54 -04:00
postgres_fdw--1.0.sql
postgres_fdw.c	Change more places to be less trusting of RestrictInfo.is_pushed_down.	2018-04-20 15:19:16 -04:00
postgres_fdw.control
postgres_fdw.h	postgres_fdw: Move function prototype to correct section.	2017-06-22 12:44:53 -04:00
shippable.c	Update copyright via script for 2017	2017-01-03 13:48:53 -05:00