From: | Heiko Wundram <modelnine(at)modelnine(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Limiting number of connections to PostgreSQL per IP (not per DB/user)? |
Date: | 2011-11-29 13:49:37 |
Message-ID: | 4ED4E2F1.5060003@modelnine.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello!
Sorry for that subscribe post I've just sent, that was bad reading on my
part (for the subscribe info on the homepage).
Anyway, the title says it all: is there any possibility to limit the
number of connections that a client can have concurrently with a
PostgreSQL-Server with "on-board" means (where I can't influence which
user/database the clients use, rather, the clients mostly all use the
same user/database, and I want to make sure that a single client which
runs amok doesn't kill connectivity for other clients)? I could surely
implement this with a proxy sitting in front of the server, but I'd
rather implement this with PostgreSQL directly.
I'm using (and need to stick with) PostgreSQL 8.3 because of the
frontend software in question.
Thanks for any hints!
--
--- Heiko.
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2011-11-29 13:59:57 | Re: PLPGSQL: How can I get the effected rows when use "execute" command in function |
Previous Message | Andy Chambers | 2011-11-29 13:28:24 | immutable functions |