From: Euler Taveira <euler@eulerto.com>
To: pgsql-bugs@lists.postgresql.org
Subject: Re: Postgresql15 crash with :FATAL: could not open shared memory segment "/PostgreSQL.0000000": No such file or directory
Date: Mon, 21 Aug 2023 12:23:55 -0300
Message-ID: <4e64ce95-9186-4003-a980-ebeae2f49aad@app.fastmail.com> (raw)
In-Reply-To: <JN3P275MB230332409437F8A412BA938DF71AA@JN3P275MB2303.ZAFP275.PROD.OUTLOOK.COM>
References: <JN3P275MB230332409437F8A412BA938DF71AA@JN3P275MB2303.ZAFP275.PROD.OUTLOOK.COM>
On Thu, Aug 17, 2023, at 5:27 PM, Emile Amewoto (ZA) wrote:
>
> Postgres version 15 randomly crash with the following error : FATAL: could not open shared memory segment "/PostgreSQL.2771626404": No such file or directory
>
You didn't provide enough information about your environment (operating system,
exact Postgres version, Postgres settings, etc).
I don't know if it is your exact problem but systemd contains a setting that
removes IPC during the logout. It means that if you are using the Postgres
service account (generally the 'postgres' user) to execute administrative tasks
and you log out while you're running a query (that requires dynamic shared
memory) then you get this error.
See 'man 5 logind.conf' for details. If you want to avoid it, disable RemoveIPC
in /etc/systemd/logind.conf. (IIRC only Debian/Ubuntu defaults to yes; RHEL
doesn't.)
If that's not your problem then you have to provide additional information as I
said before.
--
Euler Taveira
EDB https://www.enterprisedb.com/
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-bugs@postgresql.org
Cc: euler@eulerto.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Postgresql15 crash with :FATAL: could not open shared memory segment "/PostgreSQL.0000000": No such file or directory
In-Reply-To: <4e64ce95-9186-4003-a980-ebeae2f49aad@app.fastmail.com>
* 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