From: | Filip Rembiałkowski <plk(dot)zuber(at)gmail(dot)com> |
---|---|
To: | Heiko Wundram <modelnine(at)modelnine(dot)org> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Limiting number of connections to PostgreSQL per IP (not per DB/user)? |
Date: | 2011-11-29 19:44:34 |
Message-ID: | CAP_rwwkKofPyjH+LOtA+K299yLEOXfXX53wo=jzOHP5Fr1JwgA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
no easy, "standard" way of doing this in postgres.
before we go into workarounds - what's the underlying OS?
2011/11/29 Heiko Wundram <modelnine(at)modelnine(dot)org>:
> 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.
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
From | Date | Subject | |
---|---|---|---|
Next Message | Filip Rembiałkowski | 2011-11-29 20:00:06 | Re: Extending the volume size of the data directory volume |
Previous Message | Filip Rembiałkowski | 2011-11-29 19:28:51 | Re: initdb failure on Windows 2003 |