| Type: | integer |
| Default: | 2 |
| Min: | 0 |
| Max: | 2147483647 |
| Context: | sighup |
| Restart: | false |
| Since: | 10 |
This controls how many rows on a single page can be predicate-locked before the lock is promoted to covering the whole page. The default is 2. 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
- Why does "explain analyzing" this query fnish fast (showing a parallel plan), while running the actual query without "explain analyze" doesn't?
- PostgreSQL 13 sometimes works but sometimes huge execution time
- Postgresql sequential scan slow performance on 500 million rows