Re: postgres_fdw and connection management - Mailing list pgsql-hackers

<div dir="ltr"><br />On Fri, May 23, 2014 at 8:09 AM, Sandro Santilli <<a
href="mailto:strk@keybit.net">strk@keybit.net</a>>wrote:<br />><br />> I'm evaluating use of the postgres FDW
tokeep in sync a central database<br /> > to changes made in thousand other databases, via triggers.<br />><br
/>>But as long as postgres_fdw keeps connections open for the whole lifetime<br />> of a session this conflicts
withlarge use of poolers which make sessions<br /> > virtually never expire.<br />><br />> Is there any way to
askthe postgres_fdw to close connections at the<br />> end of a transaction ? Or would it be possible at all to do
froma<br />> FDW handler ? Do you see any drawback in doing that ?<br /> ><br />> I'm willing to work on a
patch,maybe accepting an additional OPTION,<br />> if you agree on the idea.<br />><br /><br />Maybe this is a
casefor the idea pointed here [1]. One way to register a cleanup code to extensions, then we can run a command called
'DISCARDEXTENSIONS' and/or 'DISCARD ALL' to do this job.<br /><br />Unfortunately nobody comment my suggestion yet.<br
/><br/>Regards,<br /><br />[1] <a
href="http://www.postgresql.org/message-id/CAFcNs+orcZZ3-wPfa0RFuOCtq81sg=PrZuHv4-m1+j5etH6HOQ@mail.gmail.com">http://www.postgresql.org/message-id/CAFcNs+orcZZ3-wPfa0RFuOCtq81sg=PrZuHv4-m1+j5etH6HOQ@mail.gmail.com</a><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>