Re: BUG #17370: shmem lost on segfault - Mailing list pgsql-bugs

From Julien Rouhaud
Subject Re: BUG #17370: shmem lost on segfault
Date
Msg-id 20220119092828.aiy3sqoa4lwwtm2g@jrouhaud
Whole thread Raw
In response to BUG #17370: shmem lost on segfault  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #17370: shmem lost on segfault  (RekGRpth <rekgrpth@gmail.com>)
List pgsql-bugs
Hi,

On Wed, Jan 19, 2022 at 03:05:56AM +0000, PG Bug reporting form wrote:
> The following bug has been logged on the website:
> 
> Bug reference:      17370
> Logged by:          RekGRpth
> Email address:      rekgrpth@gmail.com
> PostgreSQL version: 14.1
> Operating system:   docker alpine
> Description:        
> 
> In developing my https://github.com/RekGRpth/pg_task I found strange
> behavior of shared memory segment.

This is not a postgres bug.  If you need help with developing an extension you
should send a message to -hackers.

That being said, in case of unclean shutdown (which happens if a process
segfaults), the postmaster will restart and any shared memory will be lost, so
I'm assuming that you somehow serialize a handle which isn't valid anymore
after a restart, unclean or not.



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #17370: shmem lost on segfault
Next
From: RekGRpth
Date:
Subject: Re: BUG #17370: shmem lost on segfault