If the presumed theory regarding the cause of the issue is correct — as outlined in this email <https://www.postgresql.org/message-id/CALDaNm2Pmbc-7KM3nRgZcq1EBhbdvWJSTie-st57oGuKP4O44w%40mail.gmail.com> — and no data replication occurs in this scenario <https://www.postgresql.org/message-id/CAA4eK1Jz20hnPRDtPDo2BbSt0Xf8u2zY4Tc84R0OAQN8M%3D9iCQ%40mail.gmail.com> , then the proposed fix seems ok to me. But I don’t have the expertise to fully assess the trade-offs between enforcing strict ordering across nodes and maintaining the current behavior.
> > > Also, it looks like the patch mentioned in this thread addresses the > issue: > > > https://www.postgresql.org/message-id/CALDaNm2Q_pfwiCkaV920iXEbh4D%3D5MmD_tNQm_GRGX6-MsLxoQ%40mail.gmail.com > >> > > So you are okay with a test-only fix? >
