Re: Having a problem with RoR-3.1.1 and Pg-9.1 - Mailing list pgsql-general

From James B. Byrne
Subject Re: Having a problem with RoR-3.1.1 and Pg-9.1
Date
Msg-id 2cbd74f0d85e61771f06b7888a967454.squirrel@webmail.harte-lyne.ca
Whole thread Raw
In response to Re: Having a problem with RoR-3.1.1 and Pg-9.1  (Adrian Klaver <adrian.klaver@gmail.com>)
Responses Re: Having a problem with RoR-3.1.1 and Pg-9.1  (Adrian Klaver <adrian.klaver@gmail.com>)
List pgsql-general
Obviously, I am missing something important here. The
database in question is created thusly:

CREATE DATABASE test
  WITH OWNER = devl
       ENCODING = 'UTF8'
       TABLESPACE = pg_default
       LC_COLLATE = 'en_US.UTF-8'
       LC_CTYPE = 'en_US.UTF-8'
       CONNECTION LIMIT = -1;


The manual says this:

Loading an extension requires the same privileges that
would be required to create its component objects. For
most extensions this means superuser or database owner
privileges are needed. The user who runs CREATE EXTENSION
becomes the owner of the extension for purposes of later
privilege checks, as well as the owner of any objects
created by the extension's script.

However, looking at the extension properties shows this:

-- Extension: plpgsql

-- DROP EXTENSION plpgsql;

 CREATE EXTENSION plpgsql
  SCHEMA pg_catalog
  VERSION "1.0";
ALTER EXTENSION plpgsql
  OWNER TO postgres;

So, why is the plpgsql extension in test owned by postgres
and not by devl to begin with?

--
***          E-Mail is NOT a SECURE channel          ***
James B. Byrne                mailto:ByrneJB@Harte-Lyne.ca
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3


pgsql-general by date:

Previous
From: "James B. Byrne"
Date:
Subject: Re: Having a problem with RoR-3.1.1 and Pg-9.1
Next
From: Adrian Klaver
Date:
Subject: Re: Having a problem with RoR-3.1.1 and Pg-9.1