Neil Conway wrote: > Scott Shattuck <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
