From: Alfonso Moscato <alfonso.moscato@merqurio.it>
To: 'Andres Freund' <andres@anarazel.de>
Cc: pgsql-admin@lists.postgresql.org
Subject: R: repeated out of shared memory error - not related to max_locks_per_transaction
Date: Fri, 20 Jul 2018 17:30:54 +0200
Message-ID: <019801d4203e$a650ee90$f2f2cbb0$@merqurio.it> (raw)
In-Reply-To: <20180720151421.2coikkqwpeqghdrw@alap3.anarazel.de>
References: <00a601d4201a$e2291a10$a67b4e30$@merqurio.it>
<20180720151421.2coikkqwpeqghdrw@alap3.anarazel.de>
Hi andres,
I said crazy beecause when it starts, there are many of them every few
seconds, and the only way to stop them is to restart postgres.
All of our sessions run in read_committed mode.
Regards
Alfonso
-----Messaggio originale-----
Da: Andres Freund <andres@anarazel.de>
Inviato: venerdì 20 luglio 2018 17:14
A: Alfonso Moscato <alfonso.moscato@merqurio.it>
Cc: pgsql-admin@lists.postgresql.org
Oggetto: Re: repeated out of shared memory error - not related to
max_locks_per_transaction
Hi,
On 2018-07-20 13:14:53 +0200, Alfonso Moscato wrote:
> We are getting crazy with "out of shared memory" errors, and we can't
> figure the reason.
What makes them "crazy"?
Could you please give the exact error message and statement it ran?
Are any of your sessions running with serializable isolation?
Greetings,
Andres Freund
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: alfonso.moscato@merqurio.it, andres@anarazel.de, pgsql-admin@lists.postgresql.org
Subject: Re: R: repeated out of shared memory error - not related to max_locks_per_transaction
In-Reply-To: <019801d4203e$a650ee90$f2f2cbb0$@merqurio.it>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox