Re: Installing PL/pgSQL by default

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Jasen Betts <jasen(at)xnet(dot)co(dot)nz>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Installing PL/pgSQL by default
Date: 2009-12-04 13:15:02
Message-ID: 20091204131502.GB4705@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Jasen Betts wrote:
> On 2009-12-04, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> wrote:

> > The complaint is that if plpgsql is installed by default, then it will
> > be owned by postgres rather than by the db owner, who will then not be
> > able to drop it or use grant/revoke on it.
>
> The same problem is had with schema public...

It seems to me that the solution to both problems is to be able to run
some script after database creation to fix permissions of such things.
This was proposed eons ago by Fabien Coelho IIRC but rejected because no
way to implement it was found.

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Howard Cole 2009-12-04 14:07:26 Re: Unexpected EOF on client connection
Previous Message Jasen Betts 2009-12-04 11:34:54 Re: Installing PL/pgSQL by default

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2009-12-04 13:16:45 Re: Block-level CRC checks
Previous Message Fujii Masao 2009-12-04 13:06:17 Re: Backup history file should be replicated in Streaming Replication?