From: | Sandro Santilli <strk(at)keybit(dot)net> |
---|---|
To: | Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com> |
Cc: | Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: postgres_fdw and connection management |
Date: | 2014-05-27 08:57:31 |
Message-ID: | 20140527085731.GC4926@localhost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, May 27, 2014 at 12:32:50AM -0300, Fabrízio de Royes Mello wrote:
> On Mon, May 26, 2014 at 11:47 PM, Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com>
> wrote:
> >
> > 2014-05-24 0:09 GMT+09:00 Sandro Santilli <strk(at)keybit(dot)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?
Yes, that's what I had in mind.
I'll try something along those lines.
> Makes sense... but if we use "pool_connection=true" and want to close the
> opened connection. How can we do that?
Right, I still consider hooks on DISCARD a useful addition.
--strk;
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2014-05-27 09:07:55 | Re: Spreading full-page writes |
Previous Message | Heikki Linnakangas | 2014-05-27 08:49:07 | Re: Spreading full-page writes |