aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/cache/inval.c
diff options
context:
space:
mode:
authorAndres Freund <andres@anarazel.de>2019-01-21 17:03:15 -0800
committerAndres Freund <andres@anarazel.de>2019-01-21 17:07:10 -0800
commitebcc7bf949bae614cccc6b86e3ef9b926a6e2f99 (patch)
tree5a9f6cc48918797ec64d9f894b1953983d33d8ac /src/backend/utils/cache/inval.c
parentc91560defc57f89f7e88632ea14ae77b5cec78ee (diff)
downloadpostgresql-ebcc7bf949bae614cccc6b86e3ef9b926a6e2f99.tar.gz
postgresql-ebcc7bf949bae614cccc6b86e3ef9b926a6e2f99.zip
Rephrase references to "time qualification".
Now that the relevant code has, for other reasons, moved out of tqual.[ch], it seems time to refer to visiblity rather than time qualification. Author: Andres Freund Discussion: https://postgr.es/m/20180703070645.wchpu5muyto5n647@alap3.anarazel.de
Diffstat (limited to 'src/backend/utils/cache/inval.c')
-rw-r--r--src/backend/utils/cache/inval.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/utils/cache/inval.c b/src/backend/utils/cache/inval.c
index 16903c25f45..ba28611d8cc 100644
--- a/src/backend/utils/cache/inval.c
+++ b/src/backend/utils/cache/inval.c
@@ -5,7 +5,7 @@
*
* This is subtle stuff, so pay attention:
*
- * When a tuple is updated or deleted, our standard time qualification rules
+ * When a tuple is updated or deleted, our standard visibility rules
* consider that it is *still valid* so long as we are in the same command,
* ie, until the next CommandCounterIncrement() or transaction commit.
* (See acces/heap/heapam_visibility.c, and note that system catalogs are