Re: Admin nice-to-have's
От | Neil Conway |
---|---|
Тема | Re: Admin nice-to-have's |
Дата | |
Msg-id | 871y8z1k68.fsf@klamath.dyndns.org обсуждение исходный текст |
Ответ на | Admin nice-to-have's (Scott Shattuck <ss@technicalpursuit.com>) |
Ответы |
Re: Admin nice-to-have's
Re: Admin nice-to-have's |
Список | pgsql-hackers |
Scott Shattuck <ss@technicalpursuit.com> writes: > Allow DBA/Database Owner to log in even when max_connections has > been reached so they can determine which queries are hung via > pg_stat_activity etc. and perform any other needed work to restore > stability. Allowing the database owner to login seems definately wrong: it's not unusual for many of the normal database clients to run as the owner of the database they operate on. So this would effectively disable the max_connections limit in this situation. I don't see a major problem with allowing postgres to login if the connection limit is hit (although I'm not sure it's worth the worry, when 'kill a backend executing SELECT ; psql template1 postgres' works as-is). Cheers, Neil -- Neil Conway <neilconway@rogers.com> PGP Key ID: DB3C29FC
В списке pgsql-hackers по дате отправления: