Re: Limiting per user and per db accesse (was TODO list) - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Limiting per user and per db accesse (was TODO list)
Date
Msg-id 20031218014939.GD27884@dcc.uchile.cl
Whole thread Raw
In response to Re: Limiting per user and per db accesse (was TODO list)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Limiting per user and per db accesse (was TODO list)
List pgsql-hackers
On Wed, Dec 17, 2003 at 08:30:11PM -0500, Tom Lane wrote:
> Jonathan Gardner <jgardner@jonathangardner.net> writes:
> > - -- Group www can only have 12 concurrent connections with the cluster.
> > ALTER GROUP www SET max_connections = 12;
> 
> I think group-related restrictions would be an impossible rat's nest
> to define, because there's no one-to-one correspondence between backend
> processes and groups.  Per-user and per-database make sense to me,
> because a backend does have a well-defined (session) user and a
> well-defined database.

What about roles?  Is anybody going to attack the mixed users+groups
implementation in this development cycles?

-- 
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
A male gynecologist is like an auto mechanic who never owned a car.
(Carrie Snow)


pgsql-hackers by date:

Previous
From: "Andrew Dunstan"
Date:
Subject: Re: TODO list
Next
From: Tom Lane
Date:
Subject: Re: Limiting per user and per db accesse (was TODO list)