summaryrefslogtreecommitdiff
path: root/src/backend
diff options
context:
space:
mode:
authorThomas Munro <tmunro@postgresql.org>2021-01-05 14:00:16 +1300
committerThomas Munro <tmunro@postgresql.org>2021-01-05 14:00:16 +1300
commit034510c820cd75e0410332d92b4967ef9b844936 (patch)
tree5f9bc78c86e020e8a2e25a39046e43a9daba0b42 /src/backend
parentfe05b6b620066aec313c43b6b4d6c169d0a346f7 (diff)
Replace remaining uses of "whitelist".
Instead describe the action that the list effects, or just use "list" where the meaning is obvious from context. Author: Dagfinn Ilmari Mannsåker <ilmari@ilmari.org> Discussion: https://postgr.es/m/20200615182235.x7lch5n6kcjq4aue%40alap3.anarazel.de
Diffstat (limited to 'src/backend')
-rw-r--r--src/backend/access/hash/hashvalidate.c2
-rw-r--r--src/backend/utils/adt/lockfuncs.c2
2 files changed, 2 insertions, 2 deletions
diff --git a/src/backend/access/hash/hashvalidate.c b/src/backend/access/hash/hashvalidate.c
index 84625400176..1e343df0afc 100644
--- a/src/backend/access/hash/hashvalidate.c
+++ b/src/backend/access/hash/hashvalidate.c
@@ -312,7 +312,7 @@ check_hash_func_signature(Oid funcid, int16 amprocnum, Oid argtype)
* that are different from but physically compatible with the opclass
* datatype. In some of these cases, even a "binary coercible" check
* fails because there's no relevant cast. For the moment, fix it by
- * having a whitelist of allowed cases. Test the specific function
+ * having a list of allowed cases. Test the specific function
* identity, not just its input type, because hashvarlena() takes
* INTERNAL and allowing any such function seems too scary.
*/
diff --git a/src/backend/utils/adt/lockfuncs.c b/src/backend/utils/adt/lockfuncs.c
index 9f2c4946c92..0db8be6c917 100644
--- a/src/backend/utils/adt/lockfuncs.c
+++ b/src/backend/utils/adt/lockfuncs.c
@@ -644,7 +644,7 @@ pg_isolation_test_session_is_blocked(PG_FUNCTION_ARGS)
/*
* Check if blocked_pid is waiting for a safe snapshot. We could in
* theory check the resulting array of blocker PIDs against the
- * interesting PIDs whitelist, but since there is no danger of autovacuum
+ * interesting PIDs list, but since there is no danger of autovacuum
* blocking GetSafeSnapshot there seems to be no point in expending cycles
* on allocating a buffer and searching for overlap; so it's presently
* sufficient for the isolation tester's purposes to use a single element