Re: Admin nice-to-have's
От | Bruce Momjian |
---|---|
Тема | Re: Admin nice-to-have's |
Дата | |
Msg-id | 200208160455.g7G4t8r15334@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: Admin nice-to-have's (Neil Conway <nconway@klamath.dyndns.org>) |
Список | pgsql-hackers |
Neil Conway wrote: > 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). You would have to do it the unix kernel way when the PROC structure fills; it keeps the last slot open and only lets root use it. If this is desirable, I can add it to TODO. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania19073
В списке pgsql-hackers по дате отправления: