Re: Including PL/PgSQL by default

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Including PL/PgSQL by default
Date: 2008-02-21 19:36:39
Message-ID: 14692.1203622599@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)commandprompt(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2008-02-21 19:51:03 Re: Including PL/PgSQL by default
Previous Message D'Arcy J.M. Cain 2008-02-21 19:35:30 Re: Including PL/PgSQL by default