aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/shippable.c
diff options
context:
space:
mode:
Diffstat (limited to 'contrib/postgres_fdw/shippable.c')
-rw-r--r--contrib/postgres_fdw/shippable.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/contrib/postgres_fdw/shippable.c b/contrib/postgres_fdw/shippable.c
index c43e7e5ec59..b27f82e0155 100644
--- a/contrib/postgres_fdw/shippable.c
+++ b/contrib/postgres_fdw/shippable.c
@@ -7,7 +7,7 @@
* 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?
* 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
* 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
* 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
lookup_shippable(Oid objectId, Oid classId, PgFdwRelationInfo *fpinfo)