On Mon, May 26, 2014 at 10:47 PM, Shigeru Hanada <shigeru.han...@gmail.com> wrote: > 2014-05-24 0:09 GMT+09:00 Sandro Santilli <s...@keybit.net>: >> Indeed I tried "DISCARD ALL" in hope it would have helped, so I find >> good your idea of allowing extensions to register an hook there. >> >> Still, I'd like the FDW handler itself to possibly be configured >> to disable the pool completely as a server-specific configuration. > > Connection management seems FDW-specific feature to me. How about to > add FDW option, say pool_connection=true|false, to postgres_fdw which > allows per-server configuration?
Right... or you could have an option to close the connection at end-of-statement, end-of-transaction, or end-of-session. But quite apart from that, it seems like there ought to be a way to tell an FDW to flush its state. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
