From a039f8381f83547dec0d774b3598b8e4b75abf3a Mon Sep 17 00:00:00 2001 From: Konstantin Knizhnik Date: Tue, 14 Jan 2025 07:54:30 +0200 Subject: [PATCH] Optimize vector get last written LSN (#10360) ## Problem See https://github.com/neondatabase/neon/issues/10281 pg17 performs extra lock/unlock operation when fetching LwLSN. ## Summary of changes Perform all lookups under one lock, moving initialization of not found keys to separate loop. Related Postgres PR: https://github.com/neondatabase/postgres/pull/553 --------- 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 9c9e9a78a93a..0f8da73ed08d 160000 --- a/vendor/postgres-v17 +++ b/vendor/postgres-v17 @@ -1 +1 @@ -Subproject commit 9c9e9a78a93aebec2f6a2f54644442d35ffa245c +Subproject commit 0f8da73ed08d4fc4ee58cccea008c75bfb20baa8 diff --git a/vendor/revisions.json b/vendor/revisions.json index d182b880082d..b4d57ab709c9 100644 --- a/vendor/revisions.json +++ b/vendor/revisions.json @@ -1,7 +1,7 @@ { "v17": [ "17.2", - "9c9e9a78a93aebec2f6a2f54644442d35ffa245c" + "0f8da73ed08d4fc4ee58cccea008c75bfb20baa8" ], "v16": [ "16.6",