On Sat, 2011-01-01 at 11:06 -0500, Robert Haas wrote: > While reviewing the SQL/MED patch, I happened to notice that > ExecAlterObjectSchemaStmt calls AlterTableNamespace with a lock mode > argument of AccessExclusiveLock. Does anyone see a reason why > ShareUpdateExclusiveLock would be insufficient?
It seemed unsafe to me to do that while an object was being accessed, since it effectively changes the search_path, which is dangerous. Seems like a good change, if it really is viable. -- Simon Riggs http://www.2ndQuadrant.com/books/ PostgreSQL Development, 24x7 Support, Training and Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
