From: | Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com> |
---|---|
To: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: postgres_fdw and connection management |
Date: | 2014-05-23 14:13:50 |
Message-ID: | CAFcNs+pU+CP3K5an=Em0_i2Jzey+_LD5VFdOPRKc8VMAc58WMg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, May 23, 2014 at 8:09 AM, Sandro Santilli <strk(at)keybit(dot)net> wrote:
>
> I'm evaluating use of the postgres FDW to keep in sync a central database
> to changes made in thousand other databases, via triggers.
>
> But as long as postgres_fdw keeps connections open for the whole lifetime
> of a session this conflicts with large use of poolers which make sessions
> virtually never expire.
>
> Is there any way to ask the postgres_fdw to close connections at the
> end of a transaction ? Or would it be possible at all to do from a
> FDW handler ? Do you see any drawback in doing that ?
>
> I'm willing to work on a patch, maybe accepting an additional OPTION,
> if you agree on the idea.
>
Maybe this is a case for the idea pointed here [1]. One way to register a
cleanup code to extensions, then we can run a command called 'DISCARD
EXTENSIONS' and/or 'DISCARD ALL' to do this job.
Unfortunately nobody comment my suggestion yet.
Regards,
--
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
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Ross | 2014-05-23 14:23:57 | Re: pg_upgrade fails: Mismatch of relation OID in database 8.4 -> 9.3 |
Previous Message | Alvaro Herrera | 2014-05-23 14:10:23 | Re: wrapping in extended mode doesn't work well with default pager |