Le 18/09/2010 15:20, Luca Arzeni a écrit : > Package: pgadmin3 > Version: 1.8.4-3 > Severity: normal > File: pgadmin > > I log-in into a DB server as supaeruser (postgres, I mean). > I open a database, and point an object THAT IS NOT ON PUBLIC SCHEMA (for > example a table "my_table" on the schema "my_schema"). > I right-click on it and try to change owner (let's say that the original > owner was "my_owner" and I try to set to "other_owner"). > > If "my_schema" is not on search_path of postgres user, pgadmin complains that > "my_table" doesn't exists. > > I guess that, when working with objects out of search path, pgadmin shoud > prefix them with schema name, that is, it should not issue the command: > > ALTER TABLE my_table OWNER TO other_owner; (it fails because my_table is out > of search path) > > but > > ALTER TABLE my_schema.my_table OWNER TO other_owner; (it works, since it was > specified table full path) > > Note that the first command works fine if issued from a sql window, because > (I guess) it changes search_path before opening the session. > > Quick hack: alter search path of postgres user setting it to my_schema, then > logout and login again. Now the command works. Remember to set back the > search path of postgres user before quitting. >
I don't know when it was really fixed. 1.10.5 and 1.12.0 (to be released next monday) are fixed. It would be great if you could use an uptodate release (at least 1.10.5). -- Guillaume http://www.postgresql.fr http://dalibo.com -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
