RE: Introduce XID age and inactive timeout based replication slot invalidation
Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.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
Dear Nisha, Thanks for updating the patch! > Fixed. It is reasonable to align with other timeout parameters by > using milliseconds as the unit. It looks you just replaced to GUC_UNIT_MS, but the documentation and postgresql.conf.sample has not been changed yet. They should follow codes. Anyway, here are other comments, mostly cosmetic. 01. slot.c ``` +int replication_slot_inactive_timeout_ms = 0; ``` According to other lines, we should add a short comment for the GUC. 02. 050_invalidate_slots.pl Do you have a reason why you use the number 050? I feel it can be 043. 03. 050_invalidate_slots.pl Also, not sure the file name is correct. This file contains only a slot invalidation due to the replication_slot_inactive_timeout. But I feel current name is too general. 04. 050_invalidate_slots.pl ``` +use Time::HiRes qw(usleep); ``` This line is not needed because usleep() is not used in this file. Best regards, Hayato Kuroda FUJITSU LIMITED