| From: | Rod Taylor <rbt(at)rbt(dot)ca> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <mha(at)sollentuna(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Function to kill backend |
| Date: | 2004-04-06 19:38:26 |
| Message-ID: | 1081280306.56361.596.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Otherwise, I'll stick by my assertion that idle connection management should
> be done in the middleware and NOT by psql.
Perhaps it should be, but as PostgreSQL picks up more and more vendor
applications this is difficult for the person administrating the
database.
Consider a 3rd party application which has the issue but the support
contract is such that you cannot affect the application itself (their
support staff deals with it).
If you need connections in the database for other applications and this
3rd party program is idling on several slots...
--
Rod Taylor <rbt [at] rbt [dot] ca>
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
PGP Key: http://www.rbt.ca/signature.asc
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-04-06 19:39:59 | Re: Function to kill backend |
| Previous Message | Bruce Momjian | 2004-04-06 19:37:37 | Re: Function to kill backend |