<div dir="ltr"><br />On Mon, May 26, 2014 at 11:47 PM, Shigeru Hanada <<a
href="mailto:shigeru.hanada@gmail.com">shigeru.hanada@gmail.com</a>>wrote:<br />><br />> 2014-05-24 0:09
GMT+09:00Sandro Santilli <<a href="mailto:strk@keybit.net">strk@keybit.net</a>>:<br /> > > Indeed I tried
"DISCARDALL" in hope it would have helped, so I find<br />> > good your idea of allowing extensions to register
anhook there.<br />> ><br />> > Still, I'd like the FDW handler itself to possibly be configured<br /> >
>to disable the pool completely as a server-specific configuration.<br />><br />> Connection management seems
FDW-specificfeature to me. How about to<br />> add FDW option, say pool_connection=true|false, to postgres_fdw
which<br/> > allows per-server configuration?<br />><br /><br />Makes sense... but if we use
"pool_connection=true"and want to close the opened connection. How can we do that?<br /><br />--<br />Fabrízio de Royes
Mello<br/>Consultoria/Coaching PostgreSQL<br /> >> Timbira: <a
href="http://www.timbira.com.br">http://www.timbira.com.br</a><br/>>> Blog sobre TI: <a
href="http://fabriziomello.blogspot.com">http://fabriziomello.blogspot.com</a><br/>>> Perfil Linkedin: <a
href="http://br.linkedin.com/in/fabriziomello">http://br.linkedin.com/in/fabriziomello</a><br/> >> Twitter: <a
href="http://twitter.com/fabriziomello">http://twitter.com/fabriziomello</a></div>