Re: repeated out of shared memory error - not related to max_locks_per_transaction

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Alfonso Moscato <alfonso.moscato@xxxxxxxxxxx>
Subject: Re: repeated out of shared memory error - not related to max_locks_per_transaction
From: Rui DeSousa <rui@xxxxxxxxxxxxx>
Date: Fri, 20 Jul 2018 10:44:45 -0400
Cc: Tom Lane <tgl@xxxxxxxxxxxxx>, pgsql-admin@xxxxxxxxxxxxxxxxxxxx
In-reply-to: <016801d42037$4f5d4630$ee17d290$@merqurio.it>
References: <00a601d4201a$e2291a10$a67b4e30$@merqurio.it> <17662.1532096551@sss.pgh.pa.us> <016801d42037$4f5d4630$ee17d290$@merqurio.it>

What is the systems memory settings (cat /proc/meminfo)? How much swap space is allocated to the system? And more importantly what’s the Commit Limit?

Follow-Ups:
- R: repeated out of shared memory error - not related to max_locks_per_transaction
  - From: Alfonso Moscato

References:
- repeated out of shared memory error - not related to max_locks_per_transaction
  - From: Alfonso Moscato
- Re: repeated out of shared memory error - not related to max_locks_per_transaction
  - From: Tom Lane
- R: repeated out of shared memory error - not related to max_locks_per_transaction
  - From: Alfonso Moscato

Prev by Date: R: repeated out of shared memory error - not related to max_locks_per_transaction
Next by Date: R: repeated out of shared memory error - not related to max_locks_per_transaction
Previous by thread: R: repeated out of shared memory error - not related to max_locks_per_transaction
Next by thread: R: repeated out of shared memory error - not related to max_locks_per_transaction
Index(es):
- Date
- Thread

[Index of Archives] [KVM ARM] [KVM ia64] [KVM ppc] [Virtualization Tools] [Spice Development] [Libvirt] [Libvirt Users] [Linux USB Devel] [Linux Audio Users] [Yosemite Questions] [Linux Kernel] [Linux SCSI] [XFree86]

Powered by Linux