On Jul 4, 2011, at 10:09, Magnus Hagander wrote:
> On Mon, Jul 4, 2011 at 00:01, Michael Glaesemann <g...@seespotcode.net> wrote:
>> It would be nice to be able to set aside a few connections for
>> non-superusers, such as stats-monitoring connections. There's often no
>> reason to grant these users superuser privileges (they're just observers,
>> and security-definer functions can make anything visible that they may
>> need)), but at the same time you want them to be able to connect even when
>> the "normal" pool of slots may be full.
<snip/>
>> connection_pools={stats=3,superuser=10}
>> max_connections=100
>>
>> The connections allotted to "superuser" would have the same meaning as the
>> current superuser_reserved_connections GUC.
>>
>> Does this seem to be a useful feature to anyone else?
>
> Yeah, I'd definitely find it useful. Gives you a bit more flexibility
> than just using connection limiting on the individual user (though in
> your specific case here, that might work, if all your stats processes
> are with the same user).
Good point. It's another way to think of managing connections.
Michael Glaesemann
grzm seespotcode net
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
