Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Connection limit and Superuser
- From: "Joshua D. Drake" <jd(at)commandprompt(dot)com>
- To: Andrew Dunstan <andrew(at)dunslane(dot)net>
- Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
- Subject: Re: Connection limit and Superuser
- Date: Mon, 31 Jul 2006 08:28:50 -0700
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.
Wouldn't that break Slony's ability to connect to older postgresql versions and replicate?
Joshua D. Drake
cheers andrew ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
- Follow-Ups:
- Re: Connection limit and Superuser
- From: Andrew Dunstan
- Re: Connection limit and Superuser
- References:
- Connection limit and Superuser
- From: Rod Taylor
- Re: Connection limit and Superuser
- From: Martijn van Oosterhout
- Re: Connection limit and Superuser
- From: Andrew Dunstan
- Re: Connection limit and Superuser
- From: Tom Lane
- Re: Connection limit and Superuser
- From: Andrew Dunstan
- Connection limit and Superuser
- Prev by Date: Re: [PATCHES] extension for sql update
- Next by Date: Re: Connection limit and Superuser
- Previous by thread: Re: Connection limit and Superuser
- Next by thread: Re: Connection limit and Superuser
- Indexes: