From a9a47fb6d99785d5d272b408d251dca28b0879e3 Mon Sep 17 00:00:00 2001 From: Amit Kapila Date: Mon, 29 Jan 2024 10:12:58 +0530 Subject: [PATCH] Fix comments in ReplicationSlotAcquire(). They were incorrectly referring to a slot parameter in ReplicationSlotAcquire() which is not passed to the API. Author: Wang Wei Reviewed-by: Amit Kapila Discussion: https://postgr.es/m/OS3PR01MB6275E3CE4DC15FF8B8B80D3A9E7A2@OS3PR01MB6275.jpnprd01.prod.outlook.com --- src/backend/replication/slot.c | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/src/backend/replication/slot.c b/src/backend/replication/slot.c index f2781d0455a..110cb59783f 100644 --- a/src/backend/replication/slot.c +++ b/src/backend/replication/slot.c @@ -465,10 +465,7 @@ retry: LWLockAcquire(ReplicationSlotControlLock, LW_SHARED); - /* - * Search for the slot with the specified name if the slot to acquire is - * not given. If the slot is not found, we either return -1 or error out. - */ + /* Check if the slot exits with the given name. */ s = SearchNamedReplicationSlot(name, false); if (s == NULL || !s->in_use) {