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

From Fabrízio de Royes Mello
Subject Re: postgres_fdw and connection management
Date
Msg-id CAFcNs+qJ8Mho-iznEXxeyS58B6F8zi0hRb=RgfSgJWgp27ZqVA@mail.gmail.com
Whole thread
In response to Re: postgres_fdw and connection management  (Shigeru Hanada <shigeru.hanada@gmail.com>)
Responses Re: postgres_fdw and connection management
List pgsql-hackers

On Mon, May 26, 2014 at 11:47 PM, Shigeru Hanada <shigeru.hanada@gmail.com> wrote:
>
> 2014-05-24 0:09 GMT+09:00 Sandro Santilli <strk@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?
>

Makes sense... but if we use "pool_connection=true" and want to close the opened connection. How can we do that?

--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Spreading full-page writes
Next
From: Rahila Syed
Date:
Subject: Re: Compression of full-page-writes