From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Thom Brown <thombrown(at)gmail(dot)com> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Idle connection timeout |
Date: | 2009-10-09 23:34:13 |
Message-ID: | 20091009233413.GH5303@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thom Brown escribió:
> 2009/10/9 Bruce Momjian <bruce(at)momjian(dot)us>
>
> > Thom Brown wrote:
> > > I saw a recent blog entry where someone came up with a solution
> > > for expiring idle connections (
> > >
> > http://dividebyzeroexception.blogspot.com/2009/10/implementing-waittimeout-in-postgresql.html
> > )
> > > and I was surprised there wasn't a config option for this already.
> > > Is this something that can be considered for a future release?
> >
> > Our TODO has:
> >
> > Add idle_in_transaction_timeout GUC so locks are not held for
> > long periods of time
>
> Awesome! Thanks for the info Bruce.
This is quite a different thing though. You were talking about idle
connections; the TODO item is about idle-in-transaction connections.
(Also, keep in mind that something being in the TODO list does not mean
anyone is planning to work on it.)
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2009-10-09 23:58:39 | Looking for funding |
Previous Message | Thom Brown | 2009-10-09 22:28:42 | Re: Idle connection timeout |