Re: VM corruption on standby - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: VM corruption on standby
Date
Msg-id CAPpHfdsCVYT32mFsGxf+cQMEoxqs2MYmKK8obtrX9VuEmjnJpw@mail.gmail.com
Whole thread Raw
In response to Re: VM corruption on standby  (Andrey Borodin <x4mmm@yandex-team.ru>)
List pgsql-hackers
On Wed, Sep 3, 2025 at 9:47 AM Andrey Borodin <x4mmm@yandex-team.ru> wrote:
>
> > On 3 Sep 2025, at 11:37, Alexander Korotkov <aekorotkov@gmail.com> wrote:
> >
> > Could you, please, recheck?
>
> That patch also adds CondVar sleep in critical section. That patch is how we understood that such sleep is dangerous.
>
> Actual patch to deteact a problem is much simpler:
> ```
> diff --git a/src/backend/storage/ipc/waiteventset.c
> b/src/backend/storage/ipc/waiteventset.c
> index 7c0e66900f9..e89e1d115cb 100644
> --- a/src/backend/storage/ipc/waiteventset.c
> +++ b/src/backend/storage/ipc/waiteventset.c
> @@ -1044,6 +1044,7 @@ WaitEventSetWait(WaitEventSet *set, long timeout,
>        long            cur_timeout = -1;
>
>        Assert(nevents > 0);
> +       Assert(CritSectionCount == 0);
>
>        /*
>         * Initialize timeout if requested.  We must record the current time so
> ```
>
> Though it will fail in multixact test.

I thought that patch allows to reproduce the problem of bc22dc0e0d.
Sorry for the noise.

------
Regards,
Alexander Korotkov
Supabase



pgsql-hackers by date:

Previous
From: Dean Rasheed
Date:
Subject: Re: Refactoring: Use soft error reporting for *_opt_error functions
Next
From: jian he
Date:
Subject: fix NOT VALID NOT NULL with ALTER COLUMN SET IDENTITY