Skip site navigation (1) Skip section navigation (2)

Re: Connection limit and Superuser

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Connection limit and Superuser
Date: 2006-07-31 14:37:07
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Tom Lane wrote:

>Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>>Martijn van Oosterhout wrote:
>>>Maybe someone should look into enabling slony to not run as a
>>That was my initial reaction to this suggestion. But then I realised 
>>that it might well make sense to have a separate connection-limited 
>>superuser for Slony purposes (or any other special purpose) alongside an 
>>unlimited superuser.
>Actually, the real question in my mind is why Slony can't be trusted
>to use the right number of connections to start with.  If you don't
>trust it that far, what are you doing letting it into your database as
>superuser to start with?
>As for "connection-limited superuser", if you can't do ALTER USER SET
>on yourself then you aren't a superuser, so any such restriction is
>illusory anyway.

As a protection against malice, yes. I think Rod was more interested in 
some protection against stupidity.

Maybe the real answer is that Slony should connect as a non-superuser 
and call security definer functions for the privileged things it needs 
to do.



In response to


pgsql-hackers by date

Next:From: moisesDate: 2006-07-31 14:55:59
Subject: Postgres Process in Kernel Mode?
Previous:From: Tom LaneDate: 2006-07-31 14:35:15
Subject: Re: Relation locking and relcache load (was Re: Going for "all green" buildfarm results)

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group