Handle XLOG_OVERWRITE_CONTRECORD in DecodeXLogOp
authorAlvaro Herrera <alvherre@alvh.no-ip.org>
Mon, 1 Nov 2021 16:07:23 +0000 (13:07 -0300)
committerAlvaro Herrera <alvherre@alvh.no-ip.org>
Mon, 1 Nov 2021 16:07:23 +0000 (13:07 -0300)
Failing to do so results in inability of logical decoding to process the
WAL stream.  Handle it by doing nothing.

Backpatch all the way back.

Reported-by: Petr JelĂ­nek <petr.jelinek@enterprisedb.com>
src/backend/replication/logical/decode.c

index 571a9019f3ff82a279dda4babe6f56a955525459..006d4869b51391021ce0db3fbccf5eebbb47a7c4 100644 (file)
@@ -196,6 +196,7 @@ DecodeXLogOp(LogicalDecodingContext *ctx, XLogRecordBuffer *buf)
        case XLOG_FPI_FOR_HINT:
        case XLOG_FPI:
        case XLOG_FPI_MULTI:
+       case XLOG_OVERWRITE_CONTRECORD:
            break;
        default:
            elog(ERROR, "unexpected RM_XLOG_ID record type: %u", info);