database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-23 14:01:44 +03:00
Code Activity

Mention pg_index changes also cause relcache invalidation

Browse Source 
Amit Langote, additional line by me
This commit is contained in:
Simon Riggs
2017-04-13 10:07:21 +01:00
parent 7a3e8d7b50
commit 2c2ecddcff
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
src/backend/utils/cache/inval.c vendored
View File

@ -51,9 +51,9 @@
* PrepareToInvalidateCacheTuple() routine provides the knowledge of which * PrepareToInvalidateCacheTuple() routine provides the knowledge of which
* catcaches may need invalidation for a given tuple. * catcaches may need invalidation for a given tuple.
* *
* Also, whenever we see an operation on a pg_class or pg_attribute tuple, * Also, whenever we see an operation on a pg_class, pg_attribute, or
* we register a relcache flush operation for the relation described by that * pg_index tuple, we register a relcache flush operation for the relation
* tuple. * described by that tuple (as specified in CacheInvalidateHeapTuple()).
* *
* We keep the relcache flush requests in lists separate from the catcache * We keep the relcache flush requests in lists separate from the catcache
* tuple flush requests. This allows us to issue all the pending 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? * 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 * 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. * from being part of one relcache entry to being part of another.