Timeline for What is the root cause of 'out of shared memory ' issue?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 1 at 8:21 | comment | added | MiH | So the error indeed is the hash table reaches the limit, not exactly out of shared memory ? So I just need to increase max_pred_locks_per_transaction. | |
| Apr 1 at 7:42 | comment | added | Melkij | This is another structure that should be accessible from all database processes, therefore it is also located in the shared memory segment. There are quite a few such structures in shared memory, plus extensions can add their own. | |
| Apr 1 at 1:53 | comment | added | MiH | Thank you, but is it (max_pred_locks_per_transaction) relative to the shared memory ? | |
| Mar 31 at 13:39 | comment | added | Melkij | Damn, the second error message is really about another hash table. github.com/postgres/postgres/blob/REL_13_3/src/backend/storage/… This hash table is only about Serializable Snapshot Isolation. | |
| Mar 31 at 12:52 | comment | added | MiH | It seems that max_pred_locks_per_transaction is not in max_locks_per_transaction * ( (max_connections + autovacuum_max_workers + 1 + max_worker_processes + max_wal_senders) # this is MaxBackends + max_prepared_transactions ). So why the error message suggests increasing max_pred_locks_per_transaction ? | |
| Mar 30 at 9:09 | history | answered | Melkij | CC BY-SA 4.0 |