Do not assign max(lsn) to maxLastWrittenLsn in SetLastWrittenLSNForblokv #10474
+2
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
See #10281
SetLastWrittenLSNForBlockv
is assigning max(lsn) tomaxLastWrittenLsn
while its should contain only max LSN not present in LwLSN cache. It case unnecessary waits in PS.Summary of changes
Restore status-quo for pg17.
Related Postgres PR: neondatabase/postgres#563