Re: non-superuser reserved connections? connection pools?
От | Michael Glaesemann |
---|---|
Тема | Re: non-superuser reserved connections? connection pools? |
Дата | |
Msg-id | 8E95E517-943B-4CD8-94F7-5FA48D4963D4@seespotcode.net обсуждение исходный текст |
Ответ на | Re: non-superuser reserved connections? connection pools? (Magnus Hagander <magnus@hagander.net>) |
Список | pgsql-hackers |
On Jul 4, 2011, at 10:09, Magnus Hagander wrote: > On Mon, Jul 4, 2011 at 00:01, Michael Glaesemann <grzm@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'soften no reason to grant these users superuser privileges (they're just observers, and security-definer functionscan make anything visible that they may need)), but at the same time you want them to be able to connect even whenthe "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
В списке pgsql-hackers по дате отправления: