| From: | Andrew Sullivan <andrew(at)libertyrms(dot)info> |
|---|---|
| To: | PostgresSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: idle connection timeout ... |
| Date: | 2002-10-25 18:47:01 |
| Message-ID: | 20021025144701.U13384@mail.libertyrms.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 25, 2002 at 11:02:48AM -0400, Tom Lane wrote:
> So? If it hits the installation-wide limit, you'll have the same
> problem; and at that point the (presumably runaway) app would have
> sucked up all the connections, denying service to other apps using other
> databases. I think Marc's point here is to limit his exposure to
> misbehavior of any one client app, in a database server that is serving
> multiple clients using multiple databases.
That would indeed be a useful item. The only way to avoid such
exposure right now is to run another back end.
A
--
----
Andrew Sullivan 204-4141 Yonge Street
Liberty RMS Toronto, Ontario Canada
<andrew(at)libertyrms(dot)info> M2P 2A8
+1 416 646 3304 x110
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-10-25 19:02:52 | Re: idle connection timeout ... |
| Previous Message | Bruce David | 2002-10-25 17:50:45 | Trigger on 'create table' ? |