Thanks again, I think only schemas starting with pg_ should behave like that.Ahh, that you be pgAdmin protecting you from yourself :-) Try the following in a Query Tool (in the appropriate database): DROP SCHEMA pgagent CASCADE;
Do you think it's a bug in pgAdmin ? Poul