Add C comment about why we send cache invalidation messages for

session-local objects.
This commit is contained in:
Bruce Momjian 2011-09-05 22:08:14 -04:00
parent 56a9ed92b6
commit f458c90bff

View File

@ -812,6 +812,10 @@ ProcessCommittedInvalidationMessages(SharedInvalidationMessage *msgs,
* about CurrentCmdInvalidMsgs too, since those changes haven't touched * about CurrentCmdInvalidMsgs too, since those changes haven't touched
* the caches yet. * 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 * In any case, reset the various lists to empty. We need not physically
* free memory here, since TopTransactionContext is about to be emptied * free memory here, since TopTransactionContext is about to be emptied
* anyway. * anyway.