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 22:36:04 |
Message-ID: | 5127F2D4.9060503@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 02/22/2013 02:25 PM, Kevin Grittner wrote:
>>
>> To get owner to be bob you need to do:
>>
>> \c bob
>> set role bob;
>> create extension plpgsql;
>
> Good point, I forgot that the user was reset by \c.
>
>> Either way you still get the error on the COMMENT which is what is
>> tripping up the OP.
>
> The good news is that it seems to be fixed on HEAD:
I should have been clearer, the problem is in the dump file created from
the database. When you try to restore it chokes on the COMMENT line
unless you do the restore as a superuser.
>
> test=# drop database bob;
> DROP DATABASE
> test=# set role bob;
> SET
> test=> create database bob template template2;
> CREATE DATABASE
> test=> \c bob bob
> You are now connected to database "bob" as user "bob".
> bob=> create extension plpgsql;
> CREATE EXTENSION
> bob=> \dL
> List of languages
> Name | Owner | Trusted | Description
> ---------+-------+---------+------------------------------
> plpgsql | bob | t | PL/pgSQL procedural language
> (1 row)
>
> --
>
> 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 | JD Wong | 2013-02-22 23:46:24 | broke postgres, how to fix?? |
Previous Message | Kevin Grittner | 2013-02-22 22:25:26 | Re: Need help extripating plpgsql |