Re: Admin nice-to-have's

From: Neil Conway <nconway(at)klamath(dot)dyndns(dot)org>
To: Scott Shattuck <ss(at)technicalpursuit(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Admin nice-to-have's
Date: 2002-08-16 04:50:39
Message-ID: 871y8z1k68.fsf@klamath.dyndns.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Scott Shattuck <ss(at)technicalpursuit(dot)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(at)rogers(dot)com>
PGP Key ID: DB3C29FC

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-08-16 04:51:26 Re: [HACKERS] Better handling of parse errors
Previous Message Joe Conway 2002-08-16 04:44:53 where to put NO_MKTIME_BEFORE_1970?