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

From Aleksander Alekseev
Subject Re: VM corruption on standby
Date
Msg-id CAJ7c6TNfsDjCvQdX7ey4YfB8=WkvTAB4TD7dE2S1WLekJQh3kA@mail.gmail.com
Whole thread Raw
In response to Re: VM corruption on standby  (Aleksander Alekseev <aleksander@tigerdata.com>)
Responses Re: VM corruption on standby
List pgsql-hackers
> > This is a tricky bug. Do you also have a proposal of a particular fix?
>
> If my understanding is correct, we should make a WAL record with the
> XLH_LOCK_ALL_FROZEN_CLEARED flag *before* we modify the VM but within
> the same critical section (in order to avoid race conditions within
> the same backend).

I meant instance, not backend. Sorry for confusion.

> A draft patch is attached. It makes the test pass and doesn't seem to
> break any other tests.



pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Re: VM corruption on standby
Next
From: Peter Eisentraut
Date:
Subject: Re: headerscheck warnings with late-model gcc