From 37f580f9c70af416af9b3bcc3dd3662cad32fd65 Mon Sep 17 00:00:00 2001 From: Marco Slot Date: Tue, 16 Feb 2016 14:04:12 +0100 Subject: [PATCH] Trim comment about invalidating dropped relations --- src/backend/distributed/utils/metadata_cache.c | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/src/backend/distributed/utils/metadata_cache.c b/src/backend/distributed/utils/metadata_cache.c index b670f0384..ec034e2b6 100644 --- a/src/backend/distributed/utils/metadata_cache.c +++ b/src/backend/distributed/utils/metadata_cache.c @@ -477,9 +477,7 @@ master_dist_partition_cache_invalidate(PG_FUNCTION_ARGS) /* * Invalidate relcache for the relevant relation(s). In theory * logicalrelid should never change, but it doesn't hurt to be - * paranoid. We ignore the case that there's no corresponding pg_class - * entry - that happens if the pg_dist_partition tuple is deleted after - * the relation has been dropped. + * paranoid. */ if (oldLogicalRelationId != InvalidOid && oldLogicalRelationId != newLogicalRelationId) @@ -537,9 +535,7 @@ master_dist_shard_cache_invalidate(PG_FUNCTION_ARGS) /* * Invalidate relcache for the relevant relation(s). In theory * logicalrelid should never change, but it doesn't hurt to be - * paranoid. We ignore the case that there's no corresponding pg_class - * entry - that happens if the pg_dist_shard tuple is deleted after - * the relation has been dropped. + * paranoid. */ if (oldLogicalRelationId != InvalidOid && oldLogicalRelationId != newLogicalRelationId)