On Tue, May 11, 2021 at 2:16 PM Amul Sul <sula...@gmail.com> wrote: > I get why you think that, I wasn't very precise in briefing the problem. > > Any new backend that gets connected right after the shared memory > state changes to WALPROHIBIT_STATE_GOING_READ_WRITE will be by > default allowed to do the WAL writes. Such backends can perform write > operation before the checkpointer does the XLogAcceptWrites().
Okay, make sense now. But my next question is why do we allow backends to write WAL in WALPROHIBIT_STATE_GOING_READ_WRITE state? why don't we wait until the shared memory state is changed to WALPROHIBIT_STATE_READ_WRITE? -- Regards, Dilip Kumar EnterpriseDB: http://www.enterprisedb.com
