Re: postgres_fdw and connection management

From: Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com>
To: Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: postgres_fdw and connection management
Date: 2014-05-27 02:47:31
Message-ID: CAEZqfEfQrFPE7GzywP6DjuWhTP9GY6nny8giOJdymtjXQyHgog@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

--
Shigeru HANADA

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-05-27 03:01:51 Re: fix worker_spi to run as non-dynamic background worker
Previous Message Tom Lane 2014-05-27 02:24:30 Re: Re: popen and pclose redefinitions causing many warning in Windows build