From cfff9bf8378252b4c642f2b960954194ed5a93ea Mon Sep 17 00:00:00 2001 From: Justin Pryzby Date: Wed, 6 Apr 2022 07:24:48 -0500 Subject: [PATCH 14/19] duplicate words 3f1ce973467a0d285961bf2f99b11d06e264e2c1n 3500ccc39b0dadd1068a03938e4b8ff562587ccc --- src/backend/access/transam/xlogreader.c | 2 +- src/backend/replication/basebackup_server.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/backend/access/transam/xlogreader.c b/src/backend/access/transam/xlogreader.c index a5f1a648d3d..b3e37003ac5 100644 --- a/src/backend/access/transam/xlogreader.c +++ b/src/backend/access/transam/xlogreader.c @@ -300,7 +300,7 @@ XLogReleasePreviousRecord(XLogReaderState *state) /* Release the space. */ if (unlikely(record->oversized)) { - /* It's not in the the decode buffer, so free it to release space. */ + /* It's not in the decode buffer, so free it to release space. */ pfree(record); } else diff --git a/src/backend/replication/basebackup_server.c b/src/backend/replication/basebackup_server.c index bc16897b33f..33595616894 100644 --- a/src/backend/replication/basebackup_server.c +++ b/src/backend/replication/basebackup_server.c @@ -195,7 +195,7 @@ bbsink_server_end_archive(bbsink *sink) /* * We intentionally don't use data_sync_elevel here, because the server - * shouldn't PANIC just because we can't guarantee the the backup has been + * shouldn't PANIC just because we can't guarantee the backup has been * written down to disk. Running recovery won't fix anything in this case * anyway. */ -- 2.17.1