From: Andres Freund <andres@anarazel.de>
To: Alfonso Moscato <alfonso.moscato@merqurio.it>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: repeated out of shared memory error - not related to max_locks_per_transaction
Date: Fri, 20 Jul 2018 08:14:21 -0700
Message-ID: <20180720151421.2coikkqwpeqghdrw@alap3.anarazel.de> (raw)
In-Reply-To: <00a601d4201a$e2291a10$a67b4e30$@merqurio.it>
References: <00a601d4201a$e2291a10$a67b4e30$@merqurio.it>
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: andres@anarazel.de, alfonso.moscato@merqurio.it, pgsql-admin@lists.postgresql.org
Subject: Re: repeated out of shared memory error - not related to max_locks_per_transaction
In-Reply-To: <20180720151421.2coikkqwpeqghdrw@alap3.anarazel.de>
* 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