Re: limiting connections per user/database

From: Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>
To: Petr Jelínek <pjmodos(at)parba(dot)cz>
Cc: Alvaro Herrera <alvherre(at)surnet(dot)cl>, List pgsql-patches <pgsql-patches(at)postgreSQL(dot)org>, Euler Taveira de Oliveira <eulerto(at)yahoo(dot)com(dot)br>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: limiting connections per user/database
Date: 2005-06-27 14:21:23
Message-ID: 1119882083.4214.8.camel@petra
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-patches

On Sun, 2005-06-26 at 20:52 +0200, Petr Jelínek wrote:
> Alvaro Herrera wrote:
>
> >I don't think this approach is very user-friendly. I'd vote for the
> >catalog approach, I think.
> >
> >
> Ok I am fine with both but catalog changes would mean more hacking of
> ALTER DATABASE and ALTER USER.

IMHO Oracle has better solution for per-user setting:

CREATE PROFILE <name>
SESSIONS_PER_USER <int>
CONNECT_TIME <int>
IDLE_TIME <int>;

ALTER USER <name> PROFILE <name>;

karel

--
Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Heikki Linnakangas 2005-06-27 17:37:01 Re: [PATCHES] Cleaning up unreferenced table files
Previous Message Michael Fuhr 2005-06-27 13:53:23 PL/Python error checking