| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Filip Rembiałkowski <plk(dot)zuber(at)gmail(dot)com> |
| Cc: | Heiko Wundram <modelnine(at)modelnine(dot)org>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Limiting number of connections to PostgreSQL per IP (not per DB/user)? |
| Date: | 2011-11-29 22:49:55 |
| Message-ID: | 9469.1322606995@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
=?UTF-8?Q?Filip_Rembia=C5=82kowski?= <plk(dot)zuber(at)gmail(dot)com> writes:
> W dniu 29 listopada 2011 23:18 uytkownik Heiko Wundram
> <modelnine(at)modelnine(dot)org> napisa:
>> Okay, that's too bad that there's no standard way for this.
> did you look at connlimit?
> http://www.netfilter.org/projects/patch-o-matic/pom-external.html#pom-external-connlimit
Another way that we've sometimes recommended people handle custom login
restrictions is
(1) use PAM for authentication
(2) find or write a PAM plugin that makes the kind of check you want
I think that there may well be a plugin out there already that does
this, or something close enough; but you'll have to do your own
research...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2011-11-29 22:59:17 | Re: Query Optimizer makes a poor choice |
| Previous Message | Filip Rembiałkowski | 2011-11-29 22:44:47 | Re: Limiting number of connections to PostgreSQL per IP (not per DB/user)? |