Andres Freund 6939cb8c56 Hack up PREPARE/EXECUTE for nearly all distributed queries. ... All router, real-time, task-tracker plannable queries should now have full prepared statement support (and even use router when possible), unless they don't go through the custom plan interface (which basically just affects LANGUAGE SQL (not plpgsql) functions). This is achieved by forcing postgres' planner to always choose a custom plan, by assigning very low costs to plans with bound parameters (i.e. ones were the postgres planner replanned the query upon EXECUTE with all parameter values provided), instead of the generic one. This requires some trickery, because for custom plans to work the costs for a non-custom plan have to be known, which means we can't error out when planning the generic plan. Instead we have to return a "faux" plan, that'd trigger an error message if executed. But due to the custom plan logic that plan will likely (unless called by an SQL function, or because we can't support that query for some reason) not be executed; instead the custom plan will be chosen.		2017-01-23 09:23:50 -08:00
..
distributed	Hack up PREPARE/EXECUTE for nearly all distributed queries.	2017-01-23 09:23:50 -08:00
.gitignore	Initial commit of Citus 5.0	2016-02-11 04:05:32 +02:00