Limiting number of connections to PostgreSQL per IP (not per DB/user)? - Mailing list pgsql-general

From Heiko Wundram
Subject Limiting number of connections to PostgreSQL per IP (not per DB/user)?
Date
Msg-id 4ED4E2F1.5060003@modelnine.org
Whole thread Raw
Responses Re: Limiting number of connections to PostgreSQL per IP (not per DB/user)?  (Merlin Moncure <mmoncure@gmail.com>)
Re: Limiting number of connections to PostgreSQL per IP (not per DB/user)?  (Tomas Vondra <tv@fuzzy.cz>)
Re: Limiting number of connections to PostgreSQL per IP (not per DB/user)?  (Filip Rembiałkowski <plk.zuber@gmail.com>)
List 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.

pgsql-general by date:

Previous
From: Andy Chambers
Date:
Subject: immutable functions
Next
From: Muiz
Date:
Subject: PLPGSQL: How can I get the effected rows when use "execute" command in function