mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Replace remaining uses of "whitelist".

Browse Source 
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
This commit is contained in:
Thomas Munro 2021-01-05 14:00:16 +13:00
parent fe05b6b620
commit 034510c820
5 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
contrib/postgres_fdw/postgres_fdw.h
View File

@ -77,7 +77,7 @@ typedef struct PgFdwRelationInfo
bool use_remote_estimate; bool use_remote_estimate;
Cost fdw_startup_cost; Cost fdw_startup_cost;
Cost fdw_tuple_cost; Cost fdw_tuple_cost;
List *shippable_extensions; /* OIDs of whitelisted extensions */ List *shippable_extensions; /* OIDs of shippable extensions */
/* Cached catalog information. */ /* Cached catalog information. */
ForeignTable *table; ForeignTable *table;

4
contrib/postgres_fdw/shippable.c
View File

@ -7,7 +7,7 @@
* data types are shippable to a remote server for execution --- that is, * data types are shippable to a remote server for execution --- that is,
* do they exist and have the same behavior remotely as they do locally? * do they exist and have the same behavior remotely as they do locally?
* Built-in objects are generally considered shippable. Other objects can * Built-in objects are generally considered shippable. Other objects can
* be shipped if they are white-listed by the user. * be shipped if they are declared as such by the user.
* *
* Note: there are additional filter rules that prevent shipping mutable * Note: there are additional filter rules that prevent shipping mutable
* functions or functions using nonportable collations. Those considerations * functions or functions using nonportable collations. Those considerations
@ -110,7 +110,7 @@ InitializeShippableCache(void)
* *
* Right now "shippability" is exclusively a function of whether the object * Right now "shippability" is exclusively a function of whether the object
* belongs to an extension declared by the user. In the future we could * belongs to an extension declared by the user. In the future we could
* additionally have a whitelist of functions/operators declared one at a time. * additionally have a list of functions/operators declared one at a time.
*/ */
static bool static bool
lookup_shippable(Oid objectId, Oid classId, PgFdwRelationInfo *fpinfo) lookup_shippable(Oid objectId, Oid classId, PgFdwRelationInfo *fpinfo)

2
src/backend/access/hash/hashvalidate.c
View File

@ -312,7 +312,7 @@ check_hash_func_signature(Oid funcid, int16 amprocnum, Oid argtype)
* that are different from but physically compatible with the opclass * that are different from but physically compatible with the opclass
* datatype. In some of these cases, even a "binary coercible" check * datatype. In some of these cases, even a "binary coercible" check
* fails because there's no relevant cast. For the moment, fix it by * 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 * identity, not just its input type, because hashvarlena() takes
* INTERNAL and allowing any such function seems too scary. * INTERNAL and allowing any such function seems too scary.
*/ */

2
src/backend/utils/adt/lockfuncs.c
View File

@ -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 * Check if blocked_pid is waiting for a safe snapshot. We could in
* theory check the resulting array of blocker PIDs against the * 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 * blocking GetSafeSnapshot there seems to be no point in expending cycles
* on allocating a buffer and searching for overlap; so it's presently * on allocating a buffer and searching for overlap; so it's presently
* sufficient for the isolation tester's purposes to use a single element * sufficient for the isolation tester's purposes to use a single element

4
src/tools/pginclude/README
View File

@ -64,7 +64,7 @@ with no prerequisite headers other than postgres.h (or postgres_fe.h
or c.h, as appropriate). or c.h, as appropriate).
A small number of header files are exempted from this requirement, A small number of header files are exempted from this requirement,
and are whitelisted in the headerscheck script. and are skipped by the headerscheck script.
The easy way to run the script is to say "make -s headerscheck" in The easy way to run the script is to say "make -s headerscheck" in
the top-level build directory after completing a build. You should the top-level build directory after completing a build. You should
@ -86,7 +86,7 @@ the project's coding language is C, some people write extensions in C++,
so it's helpful for include files to be C++-clean. so it's helpful for include files to be C++-clean.
A small number of header files are exempted from this requirement, A small number of header files are exempted from this requirement,
and are whitelisted in the cpluspluscheck script. and are skipped by the cpluspluscheck script.
The easy way to run the script is to say "make -s cpluspluscheck" in The easy way to run the script is to say "make -s cpluspluscheck" in
the top-level build directory after completing a build. You should the top-level build directory after completing a build. You should