Re: Postgresql15 crash with :FATAL: could not open shared memory segment "/PostgreSQL.0000000": No such file or directory - Mailing list pgsql-bugs

From Euler Taveira
Subject Re: Postgresql15 crash with :FATAL: could not open shared memory segment "/PostgreSQL.0000000": No such file or directory
Date
Msg-id 4e64ce95-9186-4003-a980-ebeae2f49aad@app.fastmail.com
Whole thread Raw
In response to Postgresql15 crash with :FATAL: could not open shared memory segment "/PostgreSQL.0000000": No such file or directory  ("Emile Amewoto (ZA)" <Emile.Amewoto@absa.africa>)
Responses Re: Postgresql15 crash with :FATAL: could not open shared memory segment "/PostgreSQL.0000000": No such file or directory  (Emile Amewoto <emileam@yahoo.com>)
List pgsql-bugs
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

pgsql-bugs by date:

Previous
From: Sanjay Patil
Date:
Subject: PGRES_EMPTY_QUERY from Postgre 14.3
Next
From: "David G. Johnston"
Date:
Subject: Re: PGRES_EMPTY_QUERY from Postgre 14.3