| Type: | integer |
| Default: | -2 |
| Min: | -2147483648 |
| Max: | 2147483647 |
| Context: | sighup |
| Restart: | false |
| Since: | 10 |
This controls how many pages or tuples of a single relation can be predicate-locked before the lock is promoted to covering the whole relation. Values greater than or equal to zero mean an absolute limit, while negative values mean max_pred_locks_per_transaction divided by the absolute value of this setting. The default is -2, which keeps the behavior from previous versions of PostgreSQL. This parameter can only be set in the postgresql.conf file or on the server command line.
On StackOverflow
- Postgresql going mad
- Geoserver WFS + PostgreSQL with large table impossibly slow
- PostgreSQL 13 sometimes works but sometimes huge execution time
- Java Hibernate insert hypertable in timescaledb is very slow
- Why does "explain analyzing" this query fnish fast (showing a parallel plan), while running the actual query without "explain analyze" doesn't?