Possible defects with extensions in pgadmin3-1.14.2

From: "James B(dot) Byrne" <byrnejb(at)harte-lyne(dot)ca>
To: pgadmin-support(at)postgresql(dot)org
Subject: Possible defects with extensions in pgadmin3-1.14.2
Date: 2012-02-28 22:04:24
Message-ID: e83298c42ba537e6f9ff5b939003efd4.squirrel@webmail.harte-lyne.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support


CentOS-6.2
PostgreSQL-9.1.2
PGAdmin3-1.14.2

All installed via yum from repo at postgresql.org.

I previously sent this report to the pg users list:

First:
When viewing the properties of the plpgsql extension the
sql pane of the properties window of PGAdmin incorrectly
gives the command ALTER EXTENSION 'plpgsql' OWNER TO . . .

OWNER is not valid syntax for the ALTER EXTENSION command.
Instead it should be ALTER LANGUAGE ;plpgsql' OWNER TO .
. .

Second:
I encountered a strange inconsistency with PGAdmin3-1.14.2
relating to this. After executing "ALTER LANGUAGE plpgsql
OWNER TO devl;" in the SQL query pane inside PGAdmin3 the
extension ownership change is never reflected in the
object properties pane.

Even when disconnecting and reconnecting to the server
after making the the change the properties pane of the
extension in that database continues to show the plpgsql
extension owner as postgres. psql on the other hand
immediately shows that the new language owner is as
expected following the change inside PGAdmin3.

--
*** E-Mail is NOT a SECURE channel ***
James B. Byrne mailto:ByrneJB(at)Harte-Lyne(dot)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

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Guillaume Lelarge 2012-02-28 23:00:12 Re: Possible defects with extensions in pgadmin3-1.14.2
Previous Message Bartosz Dmytrak 2012-02-28 19:53:17 Re: feature request - show role members