Do not assign max(lsn) to maxLastWrittenLsn in SetLastWrittenLSNForblokv (#10474)

## Problem

See https://github.com/neondatabase/neon/issues/10281

`SetLastWrittenLSNForBlockv` is assigning max(lsn) to
`maxLastWrittenLsn` 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: https://github.com/neondatabase/postgres/pull/563

---------

Co-authored-by: Konstantin Knizhnik <knizhnik@neon.tech>
This commit is contained in:
Konstantin Knizhnik
2025-01-24 16:57:32 +02:00
committed by GitHub
parent 7000aaaf75
commit 9f1408fdf3
2 changed files with 2 additions and 2 deletions

View File

@@ -1,7 +1,7 @@
{
"v17": [
"17.2",
"4276717f6e91023e504de355f4f21d4824074de8"
"46f9b96555e084c35dd975da9485996db9e86181"
],
"v16": [
"16.6",