postgres-github.git / summary / log / commit / refs

commit    79534f90657c37c5238e5341a111dedd26d9c0fb
Author:   Heikki Linnakangas <heikki.linnakangas@iki.fi>
Date:     Fri Apr 03 17:27:46 2026 +0000

    Change default of max_locks_per_transactions to 128
    
    The previous commits reduced the amount of memory available for locks
    by eliminating the "safety margins" and by settling the split between
    LOCK and PROCLOCK tables at startup. The allocation is now more
    deterministic, but it also means that you often hit one of the limits
    sooner than before. To compensate for that, bump up
    max_locks_per_transactions from 64 to 128. With that there is a little
    more space in the both hash tables than what was the effective maximum
    size for either table before the previous commits.
    
    This only changes the default, so if you had changed
    max_locks_per_transactions in postgresql.conf, you will still have
    fewer locks available than before for the same setting value. This
    should be noted in the release notes. A good rule of thumb is that if
    you double max_locks_per_transactions, you should be able to get as
    many locks as before.
    
    Reviewed-by: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
    Reviewed-by: Matthias van de Meent <boekewurm+postgres@gmail.com>
    Discussion: https://www.postgresql.org/message-id/e07be2ba-856b-4ff5-8313-8b58b6b4e4d0@iki.fi

[parent: e1ad034809a4]