Re: Including PL/PgSQL by default - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Including PL/PgSQL by default
Date
Msg-id 14692.1203622599@sss.pgh.pa.us
Whole thread Raw
In response to Re: Including PL/PgSQL by default  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Including PL/PgSQL by default  (Andrew Dunstan <andrew@dunslane.net>)
Re: Including PL/PgSQL by default  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Tom Lane wrote:
>> Anyway, as I said before, I don't object to installing plpgsql by
>> default.  What I do object to is installing it in a way that makes it
>> difficult for the DBA to remove it, as would be the case if it were in
>> template0 for example.

> Perhaps it can be installed in template1 after the copy, if a certain
> initdb option is passed?

Yeah, we'd have to rejigger initdb a bit.  The bigger problem is that
traditionally template0 has been seen as a backup for template1, and it
wouldn't be (quite) that if the initial contents are different.

Would it satisfy people if plpgsql were in postgres, but neither
template DB, after initdb?  This would make it available to the sort of
person who's too lazy to learn about CREATE DATABASE, and one would
think that if they can handle CREATE DATABASE then CREATE LANGUAGE
is not beyond their powers.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "D'Arcy J.M. Cain"
Date:
Subject: Re: Including PL/PgSQL by default
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Including PL/PgSQL by default