All,
In the course of debugging why a particular server required increasing
max_locks_per_transation, I found a peculiar behavior. If you do an
UPDATE which doesn't match any CE constraint on the parent table in an
inheritance chain, you get a RowExclusiveLock on every partition and
every index on every partition. However, these rowexclusivelocks have
no page or tuple reference; it's a RowExclusiveLock with no row.
Is this intentional?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
