mirror of
https://github.com/postgres/postgres.git
synced 2025-09-05 02:22:28 +03:00
Handle logical slot conflicts on standby
During WAL replay on the standby, when a conflict with a logical slot is identified, invalidate such slots. There are two sources of conflicts: 1) Using the information added in6af1793954
, logical slots are invalidated if required rows are removed 2) wal_level on the primary server is reduced to below logical Uses the infrastructure introduced in the prior commit. FIXME: add commit reference. Change InvalidatePossiblyObsoleteSlot() to use a recovery conflict to interrupt use of a slot, if called in the startup process. The new recovery conflict is added to pg_stat_database_conflicts, as confl_active_logicalslot. See6af1793954
for an overall design of logical decoding on a standby. Bumps catversion for the addition of the pg_stat_database_conflicts column. Bumps PGSTAT_FILE_FORMAT_ID for the same reason. Author: "Drouvot, Bertrand" <bertranddrouvot.pg@gmail.com> Author: Andres Freund <andres@anarazel.de> Author: Amit Khandekar <amitdkhan.pg@gmail.com> (in an older version) Reviewed-by: "Drouvot, Bertrand" <bertranddrouvot.pg@gmail.com> Reviewed-by: Andres Freund <andres@anarazel.de> Reviewed-by: Robert Haas <robertmhaas@gmail.com> Reviewed-by: Fabrízio de Royes Mello <fabriziomello@gmail.com> Reviewed-by: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com> Reviewed-by: Amit Kapila <amit.kapila16@gmail.com> Reviewed-by: Alvaro Herrera <alvherre@alvh.no-ip.org> Discussion: https://postgr.es/m/20230407075009.igg7be27ha2htkbt@awork3.anarazel.de
This commit is contained in:
@@ -2526,6 +2526,9 @@ errdetail_recovery_conflict(void)
|
||||
case PROCSIG_RECOVERY_CONFLICT_SNAPSHOT:
|
||||
errdetail("User query might have needed to see row versions that must be removed.");
|
||||
break;
|
||||
case PROCSIG_RECOVERY_CONFLICT_LOGICALSLOT:
|
||||
errdetail("User was using a logical slot that must be invalidated.");
|
||||
break;
|
||||
case PROCSIG_RECOVERY_CONFLICT_STARTUP_DEADLOCK:
|
||||
errdetail("User transaction caused buffer deadlock with recovery.");
|
||||
break;
|
||||
@@ -3143,6 +3146,12 @@ RecoveryConflictInterrupt(ProcSignalReason reason)
|
||||
InterruptPending = true;
|
||||
break;
|
||||
|
||||
case PROCSIG_RECOVERY_CONFLICT_LOGICALSLOT:
|
||||
RecoveryConflictPending = true;
|
||||
QueryCancelPending = true;
|
||||
InterruptPending = true;
|
||||
break;
|
||||
|
||||
default:
|
||||
elog(FATAL, "unrecognized conflict mode: %d",
|
||||
(int) reason);
|
||||
|
Reference in New Issue
Block a user