mirror of
https://gitlab.com/bramw/baserow.git
synced 2025-01-30 10:26:29 +00:00
1.3 KiB
1.3 KiB
PostgreSQL locking and Baserow
Exceeding max_locks_per_transaction
In a handful of Baserow features, such as snapshotting and duplicating, we take the specified database and fetch all of its tables to perform operations on them.
Unfortunately if the total number of tables in the database is very high (i.e. 5,000-10,000), it's possible to exceed
the total number of locks specified in PostgreSQL's max_locks_per_transaction
configuration setting.
To resolve this, the steps are as follows:
- Find the path to your
postgresql.conf
. Inpsql
this can be found withSHOW config_file
. - Edit the file, and find
max_locks_per_transaction
. - Increase the value. The new value will depend on a number of factors, such as what
max_connections
andmax_prepared_transactions
are set to. We recommend experimenting with higher values. - For the new value to effect, restart postgresql.
If you are hosting Baserow with a managed database, please ask your hosting provider how max_locks_per_transaction
can be increased, they may be able to increase it for you.