|
75 | 75 | *transaction but must be kept till top-level commit otherwise. For |
76 | 76 | *simplicity we keep the controlling list-of-lists in TopTransactionContext. |
77 | 77 | * |
| 78 | + *Currently, inval messages are sent without regard for the possibility |
| 79 | + *that the object described by the catalog tuple might be a session-local |
| 80 | + *object such as a temporary table. This is because (1) this code has |
| 81 | + *no practical way to tell the difference, and (2) it is not certain that |
| 82 | + *other backends don't have catalog cache or even relcache entries for |
| 83 | + *such tables, anyway; there is nothing that prevents that. It might be |
| 84 | + *worth trying to avoid sending such inval traffic in the future, if those |
| 85 | + *problems can be overcome cheaply. |
| 86 | + * |
78 | 87 | * |
79 | 88 | * Portions Copyright (c) 1996-2011, PostgreSQL Global Development Group |
80 | 89 | * Portions Copyright (c) 1994, Regents of the University of California |
@@ -811,10 +820,6 @@ ProcessCommittedInvalidationMessages(SharedInvalidationMessage *msgs, |
811 | 820 | * since they'll not have seen our changed tuples anyway. We can forget |
812 | 821 | * about CurrentCmdInvalidMsgs too, since those changes haven't touched |
813 | 822 | * the caches yet. |
814 | | - * |
815 | | - * We still send invalidation messages for session-local objects to other |
816 | | - * backends because, while other backends cannot see any tuples, they can |
817 | | - * drop tables that are session-local to another session. |
818 | 823 | * |
819 | 824 | * In any case, reset the various lists to empty. We need not physically |
820 | 825 | * free memory here, since TopTransactionContext is about to be emptied |
|