From: | Rod Taylor <pg(at)rbt(dot)ca> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Connection limit and Superuser |
Date: | 2006-07-31 13:15:26 |
Message-ID: | 1154351726.24186.301.camel@home |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 2006-07-31 at 09:06 -0400, Tom Lane wrote:
> Rod Taylor <pg(at)rbt(dot)ca> writes:
> > It appears that the superuser does not have connection limit
> > enforcement. I think this should be changed.
>
> If you're superuser, you are not subject to access restrictions,
> by definition. I cannot imagine any scenario under which the
> above would be a good idea. (Hint: it would be more likely to
> lock out manual admin connections than Slony.)
If you don't want an admin user to have a connection limit, give them
"-1" or no connection limit.
Anyway, you're right that Slony should not require superuser status but
at the moment that is rather tricky to accomplish since it wants to muck
about in the system catalogues, use pg_cancel_backend, among other
things.
--
From | Date | Subject | |
---|---|---|---|
Next Message | Csaba Nagy | 2006-07-31 13:25:27 | Re: Connection limit and Superuser |
Previous Message | Martijn van Oosterhout | 2006-07-31 13:15:20 | Re: User-defined typle similar to char(length) varchar(length) |