Re: Including PL/PgSQL by default

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org, Greg Sabino Mullane <greg(at)turnstep(dot)com>
Subject: Re: Including PL/PgSQL by default
Date: 2008-02-22 14:15:06
Message-ID: 20080222141506.GA6449@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joshua D. Drake wrote:

> I probably shouldn't be answering this at two in the morning but... As I
> understand it in a hosted environment it is quite common that a
> superuser will do this:
>
> create database foo owner foo;
>
> Database foo would get plpgsql (as would user foo) at that point
> because template1 had plpgsql.

I'm not seeing the benefit:

alvherre=# create user plpg;
CREATE ROLE
alvherre=# create database plpg owner plpg;
CREATE DATABASE
alvherre=# \c plpg plpg
Vous êtes maintenant connecté à la base de données « plpg »comme utilisateur « plpg ».
plpg=> create language plpgsql;
CREATE LANGUAGE
plpg=>

Yes, this is new in 8.3.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2008-02-22 15:15:21 Re: Linking backend in one piece
Previous Message Magnus Hagander 2008-02-22 12:07:34 Re: OSSP can be used in the windows environment now!