Peter Geoghegan <p...@heroku.com> wrote: > we exclusive lock a heap buffer (exactly one heap buffer) while > holding shared locks on btree index buffers. Is that really so > different to holding an exclusive lock on a btree buffer while > holding a shared lock on a heap buffer? Because that's what > _bt_check_unique() does today.
Is it possible to get a deadlock doing only one of those two things? Is it possible to avoid a deadlock doing both of them? -- Kevin Grittner EDB: 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
