Commit 494ec003 authored by Alvaro Herrera's avatar Alvaro Herrera

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: default avatarPetr Jelínek <petr.jelinek@enterprisedb.com>
parent f255de9a
...@@ -224,6 +224,7 @@ DecodeXLogOp(LogicalDecodingContext *ctx, XLogRecordBuffer *buf) ...@@ -224,6 +224,7 @@ DecodeXLogOp(LogicalDecodingContext *ctx, XLogRecordBuffer *buf)
case XLOG_FPW_CHANGE: case XLOG_FPW_CHANGE:
case XLOG_FPI_FOR_HINT: case XLOG_FPI_FOR_HINT:
case XLOG_FPI: case XLOG_FPI:
case XLOG_OVERWRITE_CONTRECORD:
break; break;
default: default:
elog(ERROR, "unexpected RM_XLOG_ID record type: %u", info); elog(ERROR, "unexpected RM_XLOG_ID record type: %u", info);
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment