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

From: Emile Amewoto <emileam(at)yahoo(dot)com>
To: euler(at)eulerto(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Postgresql15 crash with :FATAL: could not open shared memory segment "/PostgreSQL.0000000": No such file or directory
Date: 2023-08-21 16:20:39
Message-ID: 537973380.2573525.1692634839959@mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thanks Euler, that's exactly my problem. I will set RemoveIPC to no.Your update is very helpful, thanks again. 
My environment is Rhel 7.9
Regards, Émile 

Sent from Yahoo Mail on Android

On Mon, Aug 21, 2023 at 17:24, Euler Taveira<euler(at)eulerto(dot)com> wrote:
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/

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2023-08-21 16:30:22 Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
Previous Message Andrew Dunstan 2023-08-21 16:04:14 Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()