Files
neon/vendor/revisions.json
Konstantin Knizhnik 9f1408fdf3 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>
2025-01-24 14:57:32 +00:00

19 lines
305 B
JSON

{
"v17": [
"17.2",
"46f9b96555e084c35dd975da9485996db9e86181"
],
"v16": [
"16.6",
"3cf7ce1afab75027716d14223f95ddb300754162"
],
"v15": [
"15.10",
"355a7c69d3f907f3612eb406cc7b9c2f55d59b59"
],
"v14": [
"14.15",
"c0aedfd3cac447510a2db843b561f0c52901b679"
]
}