diff options
| author | Simon Riggs <simon@2ndQuadrant.com> | 2017-04-13 10:07:21 +0100 |
|---|---|---|
| committer | Simon Riggs <simon@2ndQuadrant.com> | 2017-04-13 10:07:21 +0100 |
| commit | 2c2ecddcffba979ce3457bce3655136b6230a127 (patch) | |
| tree | caf991d0700ee06b9bb370a80e7ccbc7d5aa9d12 /src/backend/utils/cache | |
| parent | 7a3e8d7b503c25e009b9f591554617a2434c72eb (diff) | |
| download | postgresql-2c2ecddcffba979ce3457bce3655136b6230a127.tar.gz postgresql-2c2ecddcffba979ce3457bce3655136b6230a127.zip | |
Mention pg_index changes also cause relcache invalidation
Amit Langote, additional line by me
Diffstat (limited to 'src/backend/utils/cache')
| -rw-r--r-- | src/backend/utils/cache/inval.c | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/src/backend/utils/cache/inval.c b/src/backend/utils/cache/inval.c index 8159ab340d8..55e5c8cf74d 100644 --- a/src/backend/utils/cache/inval.c +++ b/src/backend/utils/cache/inval.c @@ -51,9 +51,9 @@ * PrepareToInvalidateCacheTuple() routine provides the knowledge of which * catcaches may need invalidation for a given tuple. * - * Also, whenever we see an operation on a pg_class or pg_attribute tuple, - * we register a relcache flush operation for the relation described by that - * tuple. + * Also, whenever we see an operation on a pg_class, pg_attribute, or + * pg_index tuple, we register a relcache flush operation for the relation + * described by that tuple (as specified in CacheInvalidateHeapTuple()). * * We keep the relcache flush requests in lists separate from the catcache * tuple flush requests. This allows us to issue all the pending catcache @@ -1132,6 +1132,7 @@ CacheInvalidateHeapTuple(Relation relation, /* * Now, is this tuple one of the primary definers of a relcache entry? + * See comments in file header for deeper explanation. * * Note we ignore newtuple here; we assume an update cannot move a tuple * from being part of one relcache entry to being part of another. |