From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
---|---|
To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
Cc: | "James B(dot) Byrne" <byrnejb(at)harte-lyne(dot)ca>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Need help extripating plpgsql |
Date: | 2013-02-22 21:39:43 |
Message-ID: | 5127E59F.9010009@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 02/22/2013 11:59 AM, Kevin Grittner wrote:
> Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> wrote:
>
>> At this point I am not sure how to do this with out creating role
>> that has superuser privileges.
>
> Something like this?:
>
> -- Set up the template using database superuser.
> create database template2;
> \c template2
> drop extension plpgsql;
> vacuum freeze analyze;
> \c postgres
> update pg_database set datistemplate = true
> where datname = 'template2';
> checkpoint;
>
> -- Create a user who can own the database and plpgsql.
> create user bob with createdb;
> set role bob;
> create database bob template template2;
> \c bob
> create extension plpgsql;
If you do as above plpgsql is created as with owner postgres.
To get owner to be bob you need to do:
\c bob
set role bob;
create extension plpgsql;
Either way you still get the error on the COMMENT which is what is
tripping up the OP.
>
> --
> Kevin Grittner
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
>
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2013-02-22 22:25:26 | Re: Need help extripating plpgsql |
Previous Message | Maz Mohammadi | 2013-02-22 21:32:45 | Re: can't access through SSL |