Re: pgsql: Support invalidating replication slots due to horizon and wal_le

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: andres(at)anarazel(dot)de
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Support invalidating replication slots due to horizon and wal_le
Date: 2023-04-11 03:03:01
Message-ID: 20230411.120301.93333867350615278.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

> Support invalidating replication slots due to horizon and wal_level

This adds the following message.

+ appendStringInfo(&err_detail, _("Logical decoding on standby requires wal_level to be at least logical on the primary server"));

This message is missing a period at the end.

regards.

diff --git a/src/backend/replication/slot.c b/src/backend/replication/slot.c
index 41848f0ac6..e73fd2d13b 100644
--- a/src/backend/replication/slot.c
+++ b/src/backend/replication/slot.c
@@ -1274,7 +1274,7 @@ ReportSlotInvalidation(ReplicationSlotInvalidationCause cause,
break;

case RS_INVAL_WAL_LEVEL:
- appendStringInfo(&err_detail, _("Logical decoding on standby requires wal_level to be at least logical on the primary server"));
+ appendStringInfo(&err_detail, _("Logical decoding on standby requires wal_level to be at least logical on the primary server."));
break;
case RS_INVAL_NONE:
pg_unreachable();
--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message David Rowley 2023-04-11 04:53:42 Re: pgsql: Add VACUUM/ANALYZE BUFFER_USAGE_LIMIT option
Previous Message Kyotaro Horiguchi 2023-04-11 03:02:53 Re: pgsql: Allow logical decoding on standbys