Re: Including PL/PgSQL by default
От | Tom Lane |
---|---|
Тема | Re: Including PL/PgSQL by default |
Дата | |
Msg-id | 14692.1203622599@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Including PL/PgSQL by default (Alvaro Herrera <alvherre@commandprompt.com>) |
Ответы |
Re: Including PL/PgSQL by default
Re: Including PL/PgSQL by default |
Список | 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 по дате отправления: