Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: Limiting per user and per db accesse (was TODO list)
Date
Msg-id 15891.1071711011@sss.pgh.pa.us
Whole thread Raw
In response to Limiting per user and per db accesse (was TODO list)  (Jonathan Gardner <jgardner@jonathangardner.net>)
Responses Re: Limiting per user and per db accesse (was TODO list)
Re: Limiting per user and per db accesse (was TODO list)
List pgsql-hackers
Tree view 
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.
        regards, tom lane

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: OLAP CUBE/ROLLUP Operators and GROUP BY grouping sets
Next
From: "Andrew Dunstan"
Date:
Subject: Re: TODO list