Re: pl/pgsql enabled by default - Mailing list pgsql-hackers

From Neil Conway
Subject Re: pl/pgsql enabled by default
Date
Msg-id 427C49A9.9030503@samurai.com
Whole thread Raw
In response to Re: pl/pgsql enabled by default  (Andrew Sullivan <ajs@crankycanuck.ca>)
Responses Re: pl/pgsql enabled by default
Re: pl/pgsql enabled by default
List pgsql-hackers
Andrew Sullivan wrote:
> 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.

So would you have us disable all the non-essential builtin functions? 
(Many of which have has security problems in the past.) What about the 
builtin encoding conversions, non-btree indexes, or a myriad of features 
that not all users need or use?

What makes sense for the default configuration of an operating system 
(which by nature must be hardened against attack) does not necessarily 
make sense for a database system.

-Neil


pgsql-hackers by date:

Previous
From: "John Hansen"
Date:
Subject: Re: Patch for collation using ICU
Next
From: Tom Lane
Date:
Subject: Re: Patch for collation using ICU