rust/neon
1
0
Fork 0
mirror of https://github.com/neondatabase/neon.git synced 2026-01-10 15:02:56 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
aabf455dfbeb3efa00673c069249aaa90004f793
neon/vendor
History
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
..
postgres-v14 @ c0aedfd3ca
Check if relation has storage in calculate_relation_size (#10477)
2025-01-24 12:43:52 +00:00
postgres-v15 @ 355a7c69d3
Check if relation has storage in calculate_relation_size (#10477)
2025-01-24 12:43:52 +00:00
postgres-v16 @ 3cf7ce1afa
Check if relation has storage in calculate_relation_size (#10477)
2025-01-24 12:43:52 +00:00
postgres-v17 @ 46f9b96555
Do not assign max(lsn) to maxLastWrittenLsn in SetLastWrittenLSNForblokv (#10474)
2025-01-24 14:57:32 +00:00
revisions.json
Do not assign max(lsn) to maxLastWrittenLsn in SetLastWrittenLSNForblokv (#10474)
2025-01-24 14:57:32 +00:00