Re: Introduce XID age and inactive timeout based replication slot invalidation
Nisha Moond <nisha.moond412@gmail.com>
Commits
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add a test for commit ac0e33136a using the injection point.
- 8a695d7998be 18.0 landed
-
Invalidate inactive replication slots.
- ac0e33136abc 18.0 landed
-
Fix incorrect slot type in BuildTupleHashTableExt
- d96d1d5152f3 18.0 cited
-
Allow synced slots to have their inactive_since.
- 6f132ed693b6 17.0 landed
-
Change last_inactive_time to inactive_since in pg_replication_slots.
- 6d49c8d4b4f4 17.0 landed
-
Track last_inactive_time in pg_replication_slots.
- a11f330b5584 17.0 landed
-
Track invalidation_reason in pg_replication_slots.
- 6ae701b4378d 17.0 landed
-
Add option force_initdb to PostgreSQL::Test::Cluster:init()
- ff9e1e764fcc 17.0 cited
-
Add a failover option to subscriptions.
- 776621a5e479 17.0 cited
-
Allow setting failover property in the replication command.
- 73292404370c 17.0 cited
-
Allow to enable failover property for replication slots via SQL API.
- c393308b69d2 17.0 cited
-
Track conflict_reason in pg_replication_slots.
- 007693f2a3ac 17.0 cited
-
Log messages for replication slot acquisition and release.
- 7c3fb505b14e 17.0 cited
-
Remove vacuum_defer_cleanup_age
- 1118cd37eb61 16.0 cited
-
Fix corruption due to vacuum_defer_cleanup_age underflowing 64bit xids
- be504a3e974d 16.0 cited
-
meson: Add initial version of meson based build system
- e6927270cd18 16.0 cited
Attachments
- v78-0001-Introduce-inactive_timeout-based-replication-slo.patch (application/octet-stream) patch v78-0001
- v78-0002-Add-TAP-test-for-slot-invalidation-based-on-inac.patch (application/octet-stream) patch v78-0002
Please find the updated v78 patches after a few off-list review rounds. Here is a summary of changes in v78: patch-001: - Fixed bugs reported by Hou-san and Peter in [1] and [2]. - Fixed a race condition reported by Hou-san off-list, which could lead to an assert failure. This failure happens when the checkpointer sets the invalidation cause to idle_timeout on the first attempt, but if it later finds another process's pid active for the slot, it retries after terminating that process. By then, inactive_since may have been updated, and it determines the invalidation_cause as RS_INVAL_NONE and below assert fails: ``` Assert(!(invalidation_cause_prev != RS_INVAL_NONE && terminated && invalidation_cause_prev != invalidation_cause)); ``` - Moved the slot's idle_time calculation to the caller of ReportSlotInvalidation(). - Improved the patch commit message for better clarity. patch-002: - Fixed a bug reported by Kuroda-san - "check_extension() must be done before the CREATE EXTENSION". - Addressed a few other comments by Peter and Kuroda-san to optimize code and improve comments. [1] https://www.postgresql.org/message-id/CABdArM7eeejXEgd6t4wtBiK%3DaWc%2B%2Bgt1__WwAWm-Y_5xMVskWg%40mail.gmail.com [2] https://www.postgresql.org/message-id/CAHut%2BPtnWyOMvxb6mZHWFxqD-NdHuYL8Zp%3D-QasAQ3VvxauiMA%40mail.gmail.com -- Thanks, Nisha