aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Geoghegan <pg@bowt.ie>2023-01-02 10:18:22 -0800
committerPeter Geoghegan <pg@bowt.ie>2023-01-02 10:18:22 -0800
commit325bc54eed4ea0836a0bb715bb18342f0c1c668a (patch)
tree9005f8d5e93625cdf376806bb78ebbfda946634d
parent6daeeb1f9196e5d59aa7d5c9ef7ed67b3f3ac4b5 (diff)
downloadpostgresql-325bc54eed4ea0836a0bb715bb18342f0c1c668a.tar.gz
postgresql-325bc54eed4ea0836a0bb715bb18342f0c1c668a.zip
Adjust VACUUM hastup LP_REDIRECT comments.
The term "truncation" has been ambiguous since commit 10a8d13823 added line pointer array truncation during heap pruning. Clear things up by specifying that we're talking about rel truncation here, to match nearby comments that apply to tuples with storage.
-rw-r--r--src/backend/access/heap/vacuumlazy.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/src/backend/access/heap/vacuumlazy.c b/src/backend/access/heap/vacuumlazy.c
index 5d8fd2fb727..e962b8d72bc 100644
--- a/src/backend/access/heap/vacuumlazy.c
+++ b/src/backend/access/heap/vacuumlazy.c
@@ -1595,7 +1595,8 @@ retry:
/* Redirect items mustn't be touched */
if (ItemIdIsRedirected(itemid))
{
- prunestate->hastup = true; /* page won't be truncatable */
+ /* page makes rel truncation unsafe */
+ prunestate->hastup = true;
continue;
}