Feb 2021

1 commit
Fix "invalid spinlock number: 0" error in pg_stat_wal_receiver.
18 Feb 2021Fujii Masaomaster14beta1REL_19_STABLE14beta1REL_18_STABLE14beta1REL_17_STABLE14beta1REL_16_STABLE14beta1REL_15_STABLE14beta1REL_14_STABLE14beta1REL_13_STABLE13.3
LLM analysis, 100% surelanded as postedfrom patchset #111 of 3 reviewers saw the final version

The committed diff matches #11 exactly after removing index metadata, including both replication source files and both sysviews regression files. Fujii Masao confirmed the push in #13.

  • Michael Paquiersaw the final versiontrailerMichael reviewed the initial fix in #4, supplied the read-placement and comment changes in #10, and acknowledged the final patch in #12.
  • Thomas Munrosaw an earlier versiontrailerThomas proposed initialization in WalRcvShmemInit() in #5, prompting the subsequent initialization and reset logic changes in #9.
  • Andres Freundsaw an earlier versiontrailerAndres explained the concurrent-access hazard of repeated spinlock initialization in #8, before the initialization and reset logic was revised in #9.

Credits across 1 commit

Author
Fujii Masao1
Reviewer
Andres Freund1
Michael Paquier1
Thomas Munro1
Committer
Fujii Masao1