Add C comment about why we send cache invalidation messages for

session-local objects.

Add C comment about why we send cache invalidation messages for
session-local objects.
f458c90b · Bruce Momjian · 56a9ed92 · f458c90b
Commit f458c90b authored Sep 05, 2011 by Bruce Momjian
Hide whitespace changes
Inline Side-by-side

Showing with 4 additions and 0 deletions

src/backend/utils/cache/inval.c src/backend/utils/cache/inval.c +4 -0

No files found.
--- a/src/backend/utils/cache/inval.c
+++ b/src/backend/utils/cache/inval.c
@@ -812,6 +812,10 @@ ProcessCommittedInvalidationMessages(SharedInvalidationMessage *msgs,
 * about CurrentCmdInvalidMsgs too, since those changes haven't touched
 * the caches yet.
 *
+ * We still send invalidation messages for session-local objects to other
+ * backends because, while other backends cannot see any tuples, they can
+ * drop tables that are session-local to another session.
+ * 
 * In any case, reset the various lists to empty.  We need not physically
 * free memory here, since TopTransactionContext is about to be emptied
 * anyway.