On Thu, May 12, 2011 at 6:28 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Alexey Klyukin <al...@commandprompt.com> writes: >> After digging in the code I've found that a RowExclusiveLock is acquired on >> a pg_db_role_setting table in AlterSetting(). While the name of the locks >> suggests that it should conflict with itself, it doesn't. After I've >> replaced the lock in question with ShareUpdateExclusiveLock, the problem >> disappeared. Attached is the simple patch with these changes. > > We're not likely to do that, first because it's randomly different from > the handling of every other system catalog update,
We have very robust locking of this type for table-related DDL operations and just about none for anything else. I don't consider the latter to be a feature. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
