Re: BUG #17370: shmem lost on segfault

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: RekGRpth <rekgrpth(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17370: shmem lost on segfault
Date: 2022-01-19 09:46:07
Message-ID: 20220119094607.vdsrbseqfpruuiuk@jrouhaud
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On Wed, Jan 19, 2022 at 02:34:13PM +0500, RekGRpth wrote:
> Ok, thanks.
>
> What I should do in this case (postmaster restarts my background
> worker and shared memory is lost)?
> When I storage in bgw_extra field - everything is ok (with restarting
> after segfault), but it size too small.

I don't know, and as I said you should ask on -hackers, ideally with a good
description of how everything works or a minimal code to reproduce your
problem as it's not really clear right now.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2022-01-19 21:06:41 BUG #17371: Immutable INTERVAL to TEXT cast can cause incorrect query results
Previous Message RekGRpth 2022-01-19 09:34:13 Re: BUG #17370: shmem lost on segfault