-
Notifications
You must be signed in to change notification settings - Fork 765
Report timespans for promotion and prewarm #12730
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
9108 tests run: 8455 passed, 0 failed, 653 skipped (full report)Flaky tests (4)Postgres 17
Postgres 15
Postgres 14
Code coverage* (full report)
* collected from Rust tests only The comment gets automatically updated with the latest test results
887bea6 at 2025-07-31T10:47:10.477Z :recycle: |
323c60c
to
5e5b8ca
Compare
6c1cb11
to
5ff3e00
Compare
ef6a163
to
dd33c5b
Compare
This would have been easier to review in smaller PRs. It seems like there are 3 things going on with this one PR which you listed in the original description. Can you break it apart? |
(3) is a one-liner, so I'll separate prewarm cancellation |
Also,
Would be good to separate out. That will leave this PR in a much better state for a better review. |
Timespans reporting and fix for spec application are fine in a single PR |
abd2adc
to
887bea6
Compare
synchronous_standby_names=walproposer
for promoted endpoints. Otherwise, walproposer on promoted standby ignores reply from safekeeper and is stuck on lsn COMMIT eternally.