| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | rekgrpth(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17370: shmem lost on segfault |
| Date: | 2022-01-19 09:28:28 |
| Message-ID: | 20220119092828.aiy3sqoa4lwwtm2g@jrouhaud |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | RekGRpth | 2022-01-19 09:34:13 | Re: BUG #17370: shmem lost on segfault |
| Previous Message | PG Bug reporting form | 2022-01-19 03:05:56 | BUG #17370: shmem lost on segfault |