| From: | Thom Brown <thombrown(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Idle connection timeout |
| Date: | 2009-10-10 00:51:46 |
| Message-ID: | bddc86150910091751o48d14434ld3283286d42defca@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2009/10/10 Alvaro Herrera <alvherre(at)commandprompt(dot)com>
> > > 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.)
>
>
Oh, I see. Yes, that is different. In which case, I'd still like to see
such a feature implemented as I imagine it could be useful for auto-killing
connections not being used that are continuously taking some of the
resources.
Thom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-10-10 02:01:07 | Re: Using results from INSERT ... RETURNING |
| Previous Message | David Fetter | 2009-10-10 00:49:33 | Re: Concurrency testing |