I think that plpgsql should be maintained in core, enabled
by default with the ability to turn it off. This handles
the paranoid dba and security issue while giving the majority
of people what they already have by default. Of course
the dump create language statements will have to be dealt with
and any other small gotchas. A large gotcha might be a reason
to not do it, but I have not seen mention of any.
--elein
elein@varlena.com
On Fri, May 06, 2005 at 12:19:12PM -0400, Andrew Sullivan wrote:
> On Fri, May 06, 2005 at 03:37:21PM +1000, Neil Conway wrote:
> >
> > But I agree security is not a good argument against enabling it by default.
>
> Sure it is. "Don't enable anything you don't need," is the first
> security rule. Everything is turned off by default. If you want it,
> enable it.
>
> "Enabled by default" is what made early Linux distributions give
> old UNIX hands the willies. It was bad enough that IRIX shipped with
> everything turned on and suid root; at least it cost several thousand
> dollars. Linux was _free_, and had many of the same problems.
>
> A
>
> --
> Andrew Sullivan | ajs@crankycanuck.ca
> In the future this spectacle of the middle classes shocking the avant-
> garde will probably become the textbook definition of Postmodernism.
> --Brad Holland
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>