From: Julien Rouhaud <rjuju123@gmail.com>
To: rekgrpth@gmail.com
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17370: shmem lost on segfault
Date: Wed, 19 Jan 2022 17:28:28 +0800
Message-ID: <20220119092828.aiy3sqoa4lwwtm2g@jrouhaud> (raw)
In-Reply-To: <17370-a42a313cf1589256@postgresql.org>
References: <17370-a42a313cf1589256@postgresql.org>
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.
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-bugs@postgresql.org
Cc: rjuju123@gmail.com, rekgrpth@gmail.com
Subject: Re: BUG #17370: shmem lost on segfault
In-Reply-To: <20220119092828.aiy3sqoa4lwwtm2g@jrouhaud>
References: <17370-a42a313cf1589256@postgresql.org> <20220119092828.aiy3sqoa4lwwtm2g@jrouhaud>
* 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