v4-0003-fixup-is_schema_sent-set-too-early.patch
application/octet-stream
Filename: v4-0003-fixup-is_schema_sent-set-too-early.patch
Type: application/octet-stream
Part: 2
Patch
Same data as JSON:
GET /api/v1/attachments/:id/patch
the parsed metadata as JSON — format, series position, per-file stats; never the diff bytes.
API reference →
Format: format-patch
Series: patch v4-0003
Subject: fixup: is_schema_sent set too early
| File | + | − |
|---|---|---|
| src/backend/replication/logical/reorderbuffer.c | 0 | 1 |
From 5c284042e2a21f7f7ed7bdc84a5eccec77e4c05f Mon Sep 17 00:00:00 2001 From: Tomas Vondra <tomas@2ndquadrant.com> Date: Fri, 27 Dec 2019 22:50:55 +0100 Subject: [PATCH v4 03/19] fixup: is_schema_sent set too early --- src/backend/replication/logical/reorderbuffer.c | 1 - 1 file changed, 1 deletion(-) diff --git a/src/backend/replication/logical/reorderbuffer.c b/src/backend/replication/logical/reorderbuffer.c index b1feff3..c0b9725 100644 --- a/src/backend/replication/logical/reorderbuffer.c +++ b/src/backend/replication/logical/reorderbuffer.c @@ -1819,7 +1819,6 @@ ReorderBufferCommit(ReorderBuffer *rb, TransactionId xid, * about the message itself? */ LocalExecuteInvalidationMessage(&change->data.inval.msg); - txn->is_schema_sent = false; break; case REORDER_BUFFER_CHANGE_INTERNAL_TUPLECID: -- 1.8.3.1