Handle XLOG_OVERWRITE_CONTRECORD in DecodeXLogOp

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>

diff --git a/src/backend/replication/logical/decode.c b/src/backend/replication/logical/decode.c
index 676f921c1eab99c9a888d6fce5742e81e58a569c..c085f7b0f3924707b896d9fd4690b8a3da60584c 100644 (file)
--- a/src/backend/replication/logical/decode.c
+++ b/src/backend/replication/logical/decode.c
@@ -200,6 +200,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);