Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vzF7F-000peF-0b for pgsql-hackers@arkaria.postgresql.org; Sun, 08 Mar 2026 14:28:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vzF7D-00Alaf-1B for pgsql-hackers@arkaria.postgresql.org; Sun, 08 Mar 2026 14:28:19 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vzF7D-00AlaX-0I for pgsql-hackers@lists.postgresql.org; Sun, 08 Mar 2026 14:28:19 +0000 Received: from mail-pl1-x633.google.com ([2607:f8b0:4864:20::633]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1vzF7B-00000001V4V-1isw for pgsql-hackers@lists.postgresql.org; Sun, 08 Mar 2026 14:28:19 +0000 Received: by mail-pl1-x633.google.com with SMTP id d9443c01a7336-2a9296b3926so82757635ad.1 for ; Sun, 08 Mar 2026 07:28:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1772980095; x=1773584895; darn=lists.postgresql.org; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=NZEJYITCExyoYe2oW6YGsvIYq9sEyQ2hU6PVcFi6NCU=; b=L6AWs1WwUGSZdEinOL1q4XJaZgwLGdIpENQQkQWCOecFqISyuP1NdZPhi/JrlRkgdq JLLsTM3mn91pQAZ2LMQAKIEnEBfPte5FNGk/1TMfuhrVY+2jjMXnLgn+lzNrscUKZE78 FBt5hXzF2MXe1y+l0/VfPy6H7Or0Gba2xqQDVt/WzRkKWKJRDrhpTQoxtg5eCZZ4bhJb sex23Bz5P33nZrmcSru33XfKJKReFffxaLJGOaIRVnAoagYp2n5JewZhtUQOaVNMdG4g YKcf7RxV75W0i8z+7TsZhzBAGVr8jsEwl9tBdH3Rb01q9EzLNkagn30oi1z6OejGwG8P FIWg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1772980095; x=1773584895; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=NZEJYITCExyoYe2oW6YGsvIYq9sEyQ2hU6PVcFi6NCU=; b=fHVS+Zr9OE6TT0VktQZUyOvrFHcVJdwqG/6ZPq6UMGsOS8K3bFwxkKiU6Q4hPS5e6z 3+a5KoNNLfZe60kD+onzPPgk2UoKFepmN6f2P+J5UPQynX9Gwpu3Podwkh6UMsWPrO01 dfS/ytQ9UoFh3UOBnG9IvPQhqnnNbqfIw30AdAM2Z7CsVbLnzI2FQPyGEYpCiFdRSXmM V6zVTHEmP8mRf82wMaJFstOeO0PkXM6KVMYHxwtpiICiT/HZAOz5/c+UHUGkejuPcQw7 MuqLY11YPvDB4eiMUprVEnaz7uu+ubBpMMyYNYk9WCxszJgch4aTtQAdWoR/A5GFgez1 HBUg== X-Gm-Message-State: AOJu0YwwHTg7Y9mukUywTn4GOgVIcQD+20zkrn5hMuCIqmzKbbsKqpC0 tI/qNwp7bfL72RvNbjp6hap1vONJVlPICQAY1K3ufjSnRCP+0SQ8pD2sJmvPHw== X-Gm-Gg: ATEYQzx2U1M0f2++vml6MPLqPoSjJEAnjAEj3og6MmUtUummx/7Q0KWgUm1AxUTqZ9S nSL3u1r4zsy7kdd9rd2vumRjKQQ8v0PkqggRuOBghzAPH+aM0TiNKgjxOLrP80p7xOelD/pvYe3 CO+DJX/iPt7WQDahdawWZmSod/NGeoGmxVkQn7AlrZc3UNxcJrErHRfre1lwO2N8iL/gKbheq6b nWOCf3gHHIM4kAUaUu+XAxC/BsbOxty+J1+wFZYRNEjKsW0UTKm2o8hjOlRJ3nxjUxUehgM7LTS Z2kOi+JkRKybAidY/XfzCvqTvEoOzrmT29Q78mvzaOfpP6pFhHev45pCf7kg470ADuM95X5WMGO kBMabdZ4OrVDjU48dI2UVqeuQXgE9dl3UOFew7MkO8NLi8bqaPssqTIfyQU5T3dKI7CFJaM4rLk zASyYJcMzRq59vwVjSl0LY5h0nbsc= X-Received: by 2002:a17:903:120f:b0:2ae:670e:309f with SMTP id d9443c01a7336-2ae824f4d5fmr82163765ad.34.1772980094582; Sun, 08 Mar 2026 07:28:14 -0700 (PDT) Received: from sahitya-07.. ([2401:4900:8854:2f63:2aba:be30:9ae:c23a]) by smtp.gmail.com with ESMTPSA id d9443c01a7336-2ae83fa2fa5sm84750745ad.70.2026.03.08.07.28.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 08 Mar 2026 07:28:13 -0700 (PDT) From: Sahitya Chandra To: pgsql-hackers@lists.postgresql.org Cc: Sahitya Chandra Subject: [PATCH] Remove trailing period from errmsg in subscriptioncmds.c Date: Sun, 8 Mar 2026 19:58:06 +0530 Message-ID: <20260308142806.181309-1-sahityajb@gmail.com> X-Mailer: git-send-email 2.43.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, While reading the subscription code I noticed one error message that doesn't follow the project's style: in check_remote_recovery_state() in subscriptioncmds.c, the errmsg() for the "publisher is in recovery" case ends with a period. The convention elsewhere (including the similar message a few lines above in the same file) is no trailing period. The attached one-line patch removes the trailing period from that string. No behavior change. Thanks, Sahitya Chandra --- src/backend/commands/subscriptioncmds.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/backend/commands/subscriptioncmds.c b/src/backend/commands/subscriptioncmds.c index 9e21d7a7df9..724637cff5b 100644 --- a/src/backend/commands/subscriptioncmds.c +++ b/src/backend/commands/subscriptioncmds.c @@ -2993,7 +2993,7 @@ check_pub_dead_tuple_retention(WalReceiverConn *wrconn) if (remote_in_recovery) ereport(ERROR, errcode(ERRCODE_FEATURE_NOT_SUPPORTED), - errmsg("cannot enable retain_dead_tuples if the publisher is in recovery.")); + errmsg("cannot enable retain_dead_tuples if the publisher is in recovery")); ExecDropSingleTupleTableSlot(slot); -- 2.43.0