From 9f1408fdf3c4cc79ad3e1810c4e4c76a80a695a9 Mon Sep 17 00:00:00 2001 From: Konstantin Knizhnik Date: Fri, 24 Jan 2025 16:57:32 +0200 Subject: [PATCH] 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 --- vendor/postgres-v17 | 2 +- vendor/revisions.json | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/vendor/postgres-v17 b/vendor/postgres-v17 index 4276717f6e..46f9b96555 160000 --- a/vendor/postgres-v17 +++ b/vendor/postgres-v17 @@ -1 +1 @@ -Subproject commit 4276717f6e91023e504de355f4f21d4824074de8 +Subproject commit 46f9b96555e084c35dd975da9485996db9e86181 diff --git a/vendor/revisions.json b/vendor/revisions.json index dba0e67fb4..3aa42d22c5 100644 --- a/vendor/revisions.json +++ b/vendor/revisions.json @@ -1,7 +1,7 @@ { "v17": [ "17.2", - "4276717f6e91023e504de355f4f21d4824074de8" + "46f9b96555e084c35dd975da9485996db9e86181" ], "v16": [ "16.6",