Possible defects with extensions in pgadmin3-1.14.2 - Mailing list pgadmin-support

From James B. Byrne
Subject Possible defects with extensions in pgadmin3-1.14.2
Date
Msg-id e83298c42ba537e6f9ff5b939003efd4.squirrel@webmail.harte-lyne.ca
Whole thread Raw
Responses Re: Possible defects with extensions in pgadmin3-1.14.2
List 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@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



pgadmin-support by date:

Previous
From: Bartosz Dmytrak
Date:
Subject: Re: feature request - show role members
Next
From: Guillaume Lelarge
Date:
Subject: Re: Possible defects with extensions in pgadmin3-1.14.2