You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Track invalidation_reason in pg_replication_slots.
Till now, the reason for replication slot invalidation is not trackeddirectly in pg_replication_slots. A recent commit007693f added'conflict_reason' to show the reasons for slot conflict/invalidation, butonly for logical slots.This commit adds a new column 'invalidation_reason' to show invalidationreasons for both physical and logical slots. And, this commit also turns'conflict_reason' text column to 'conflicting' boolean column (effectivelyreverting commit007693f). The 'conflicting' column is true forinvalidation reasons 'rows_removed' and 'wal_level_insufficient' becausethose make the slot conflict with recovery. When 'conflicting' is true,one can now look at the new 'invalidation_reason' column for the reasonfor the logical slot's conflict with recovery.The new 'invalidation_reason' column will also be useful to track otherinvalidation reasons in the future commit.Author: Bharath RupireddyReviewed-by: Bertrand Drouvot, Amit Kapila, Shveta MalikDiscussion:https://www.postgresql.org/message-id/ZfR7HuzFEswakt/a%40ip-10-97-1-34.eu-west-3.compute.internalDiscussion:https://www.postgresql.org/message-id/CALj2ACW4aUe-_uFQOjdWCEN-xXoLGhmvRFnL8SNw_TZ5nJe+aw@mail.gmail.com