Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 9da2224

Browse files
author
Amit Kapila
committed
Fix typo in reorderbuffer.c.
Author: Zhijie Hou Reviewed-by: Sawada Masahiko Discussion: https://postgr.es/m/ba88bb58aaf14284abca16aec04bf279@G08CNEXMBPEKD05.g08.fujitsu.local
1 parent 034510c commit 9da2224

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

src/backend/replication/logical/reorderbuffer.c

+7-7
Original file line numberDiff line numberDiff line change
@@ -2119,13 +2119,13 @@ ReorderBufferProcessTXN(ReorderBuffer *rb, ReorderBufferTXN *txn,
21192119
* Mapped catalog tuple without data, emitted while
21202120
* catalog table was in the process of being rewritten. We
21212121
* can fail to look up the relfilenode, because the
2122-
* relmapper has no "historic" view, in contrast to normal
2123-
* the normal catalog during decoding. Thus repeated
2124-
* rewrites can cause a lookup failure. That's OK because
2125-
* we do not decode catalog changes anyway. Normally such
2126-
* tuples would be skipped over below, but we can't
2127-
* identify whether the table should be logically logged
2128-
* without mapping the relfilenode to the oid.
2122+
* relmapper has no "historic" view, in contrast to the
2123+
* normal catalog during decoding. Thus repeated rewrites
2124+
* can cause a lookup failure. That's OK because we do not
2125+
* decode catalog changes anyway. Normally such tuples
2126+
* would be skipped over below, but we can't identify
2127+
* whether the table should be logically logged without
2128+
* mapping the relfilenode to the oid.
21292129
*/
21302130
if (reloid == InvalidOid &&
21312131
change->data.tp.newtuple == NULL &&

0 commit comments

Comments
 (0)