Re: Limiting per user and per db accesse (was TODO list)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jonathan Gardner <jgardner(at)jonathangardner(dot)net>
Cc: David Felstead <David(dot)Felstead(at)colesmyer(dot)com(dot)au>, "'Postgresql Hackers'" <pgsql-hackers(at)postgresql(dot)org>, "'Andrew Dunstan'" <andrew(at)dunslane(dot)net>
Subject: Re: Limiting per user and per db accesse (was TODO list)
Date: 2003-12-18 01:30:11
Message-ID: 15891.1071711011@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jonathan Gardner <jgardner(at)jonathangardner(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2003-12-18 01:35:20 Re: TODO list
Previous Message Tom Lane 2003-12-18 01:20:03 Re: OLAP CUBE/ROLLUP Operators and GROUP BY grouping sets