Skip site navigation (1) Skip section navigation (2)

Re: Having a problem with RoR-3.1.1 and Pg-9.1

From: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Cc: "James B(dot) Byrne" <byrnejb(at)harte-lyne(dot)ca>
Subject: Re: Having a problem with RoR-3.1.1 and Pg-9.1
Date: 2012-02-27 21:37:24
Message-ID: 201202271337.25417.adrian.klaver@gmail.com (view raw or flat)
Thread:
Lists: pgsql-general
On Monday, February 27, 2012 1:23:22 pm James B. Byrne wrote:
> 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;

When you run the above are you doing it as user dev1 or the postgres user?

> 
> 
> 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?

Is plpgsql in template1 and you are running the CREATE DATABASE script as 
postgres?  

-- 
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com

In response to

Responses

pgsql-general by date

Next:From: Donald KerrDate: 2012-02-27 21:38:50
Subject: advice on Replication for a Specific Scenario
Previous:From: James B. ByrneDate: 2012-02-27 21:23:22
Subject: Re: Having a problem with RoR-3.1.1 and Pg-9.1

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group