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

From Neil Conway
Subject Re: pl/pgsql enabled by default
Date
Msg-id 427C98A2.6090703@samurai.com
Whole thread Raw
In response to Re: pl/pgsql enabled by default  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: pl/pgsql enabled by default
List pgsql-hackers
Simon Riggs wrote:
> I support Andrew's comment, though might reword it to 
> "Don't enable anything that gives users programmable features or user
> exits by default".

Users can already define SQL functions by default, which certainly 
provides "programmable features". I'm not quite sure what you mean by 
"user exits."

I guess I'm missing how pl/pgsql is a fundamentally greater security risk.

> You can't use the builtin encoding functions or non-btree indexes to
> access things you are not supposed to.

How can you use pl/pgsql to "access things you are not supposed to"?

-Neil


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: pl/pgsql enabled by default
Next
From: Greg Stark
Date:
Subject: Re: pgFoundry