Having a problem with RoR-3.1.1 and Pg-0.1

Started by James B. Byrneabout 14 years ago2 messagesgeneral
Jump to latest
#1James B. Byrne
byrnejb@harte-lyne.ca

CentOS-5.7
RoR-3.1.1
Pg-9.1

I am trying to run a test suite against Pg-9.1 for a
RoR-3.1.1 based application. When I run the test DB setup
task it fails:

$ rake db:test:prepare
Using AdapterExtensions
psql:/...rails3/db/development_structure.sql:22: ERROR:
must be owner of extension plpgsql

The offending line in development_structure.sql is:

COMMENT ON EXTENSION plpgsql IS 'PL/pgSQL procedural
language';

The error does not happen if the target DBMS is Pg-8.4. I
recall that with 8.4 that we would see warnings relating
to trying to load/create plpgsql when it already existed
in the test database but now we are getting an error which
stops further processing. Is there a way around this?

I have already reported the problem to the Rails list in
order to discover if this is a defect or if there is some
way to avoid this issue with Pg-9.1.

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

#2Adrian Klaver
adrian.klaver@aklaver.com
In reply to: James B. Byrne (#1)
Re: Having a problem with RoR-3.1.1 and Pg-0.1

On Friday, February 24, 2012 7:16:47 am James B. Byrne wrote:

CentOS-5.7
RoR-3.1.1
Pg-9.1

I am trying to run a test suite against Pg-9.1 for a
RoR-3.1.1 based application. When I run the test DB setup
task it fails:

$ rake db:test:prepare
Using AdapterExtensions
psql:/...rails3/db/development_structure.sql:22: ERROR:
must be owner of extension plpgsql

The offending line in development_structure.sql is:

COMMENT ON EXTENSION plpgsql IS 'PL/pgSQL procedural
language';

The error does not happen if the target DBMS is Pg-8.4. I
recall that with 8.4 that we would see warnings relating
to trying to load/create plpgsql when it already existed
in the test database but now we are getting an error which
stops further processing. Is there a way around this?

See here for similar report:
http://archives.postgresql.org/pgsql-general/2012-02/msg00504.php

The options seem to be run the script as the owner of the plpgsql EXTENSION or
do not include the comment.

I have already reported the problem to the Rails list in
order to discover if this is a defect or if there is some
way to avoid this issue with Pg-9.1.

--
Adrian Klaver
adrian.klaver@gmail.com