From: | "Alfonso Moscato" <alfonso(dot)moscato(at)merqurio(dot)it> |
---|---|
To: | "'Andres Freund'" <andres(at)anarazel(dot)de> |
Cc: | <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | R: repeated out of shared memory error - not related to max_locks_per_transaction |
Date: | 2018-07-20 15:30:54 |
Message-ID: | 019801d4203e$a650ee90$f2f2cbb0$@merqurio.it |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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(at)anarazel(dot)de>
Inviato: venerdì 20 luglio 2018 17:14
A: Alfonso Moscato <alfonso(dot)moscato(at)merqurio(dot)it>
Cc: pgsql-admin(at)lists(dot)postgresql(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Alfonso Moscato | 2018-07-20 15:38:40 | R: repeated out of shared memory error - not related to max_locks_per_transaction |
Previous Message | Shreeyansh Dba | 2018-07-20 15:18:13 | Re: repeated out of shared memory error - not related to max_locks_per_transaction |