mirror of
https://github.com/postgres/postgres.git
synced 2025-07-27 12:41:57 +03:00
Prevent use of invalidated logical slot in CreateDecodingContext()
Previously we had checks for this in multiple places. Support for logical decoding on standbys will add other forms of invalidation, making it worth while to centralize the checks. This slightly changes the error message for both the walsender and SQL interface. Particularly the SQL interface error was inaccurate, as the "This slot has never previously reserved WAL" portion was unreachable. Reviewed-by: "Drouvot, Bertrand" <bertranddrouvot.pg@gmail.com> Reviewed-by: Melanie Plageman <melanieplageman@gmail.com> Discussion: https://postgr.es/m/20230407075009.igg7be27ha2htkbt@awork3.anarazel.de
This commit is contained in:
@ -1253,13 +1253,6 @@ StartLogicalReplication(StartReplicationCmd *cmd)
|
||||
|
||||
ReplicationSlotAcquire(cmd->slotname, true);
|
||||
|
||||
if (XLogRecPtrIsInvalid(MyReplicationSlot->data.restart_lsn))
|
||||
ereport(ERROR,
|
||||
(errcode(ERRCODE_OBJECT_NOT_IN_PREREQUISITE_STATE),
|
||||
errmsg("cannot read from logical replication slot \"%s\"",
|
||||
cmd->slotname),
|
||||
errdetail("This slot has been invalidated because it exceeded the maximum reserved size.")));
|
||||
|
||||
/*
|
||||
* Force a disconnect, so that the decoding code doesn't need to care
|
||||
* about an eventual switch from running in recovery, to running in a
|
||||
|
Reference in New Issue
Block a user