The shared lock table tracks locks on
max_locks_per_transaction * (max_connections + max_prepared_transactions) objects (e.g., tables); hence, no more than this many distinct objects can be locked at any one time. This parameter controls the average number of object locks allocated for each transaction; individual transactions can lock more objects as long as the locks of all transactions fit in the lock table. This is not the number of rows that can be locked; that value is unlimited. The default, 64, has historically proven sufficient, but you might need to raise this value if you have queries that touch many different tables in a single transaction, e.g. query of a parent table with many children. This parameter can only be set at server start.
When running a standby server, you must set this parameter to the same or higher value than on the master server. Otherwise, queries will not be allowed in the standby server.
- performance issue in remove_from_unowned_list()
- Re: Speed up transaction completion faster after many relations are accessed in a transaction
- Re: Recovery performance of DROP DATABASE with many tablespaces
- RE: Speed up transaction completion faster after many relations are accessed in a transaction
- RE: Recovery performance of DROP DATABASE with many tablespaces