From 57b1a6001b2910c9a8002e72f22391255e8b8bb9 Mon Sep 17 00:00:00 2001 From: Justin Pryzby Date: Sat, 23 Jul 2022 15:10:01 -0500 Subject: [PATCH 2/4] fix whitespace weird since c91560defc57f89f7e88632ea14ae77b5cec78ee --- src/backend/utils/cache/inval.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/backend/utils/cache/inval.c b/src/backend/utils/cache/inval.c index eb5782f82a4..c0e33c0f177 100644 --- a/src/backend/utils/cache/inval.c +++ b/src/backend/utils/cache/inval.c @@ -9,8 +9,8 @@ * consider that it is *still valid* so long as we are in the same command, * ie, until the next CommandCounterIncrement() or transaction commit. * (See access/heap/heapam_visibility.c, and note that system catalogs are - * generally scanned under the most current snapshot available, rather than - * the transaction snapshot.) At the command boundary, the old tuple stops + * generally scanned under the most current snapshot available, rather than + * the transaction snapshot.) At the command boundary, the old tuple stops * being valid and the new version, if any, becomes valid. Therefore, * we cannot simply flush a tuple from the system caches during heap_update() * or heap_delete(). The tuple is still good at that point; what's more, -- 2.17.1