Revise FDW planning API, again.
Further reflection shows that a single callback isn't very workable if we
desire to let FDWs generate multiple Paths, because that forces the FDW to
do all work necessary to generate a valid Plan node for each Path. Instead
split the former PlanForeignScan API into
Extend object access hook framework to support arguments, and DROP.
This allows loadable modules to get control at drop time, perhaps for the
purpose of performing additional security checks or to log the event.
The initial purpose of this code is to support sepgsql, but other
applications should
sepgsql DROP support.
KaiGai Kohei
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/e914a144d3aaa0a09e0aab031d7e6f58389401ce
Modified Files
--
contrib/sepgsql/database.c | 27 ++
contrib/sepgsql/expected/create.out | 80 -
c
