33
33
* updates and deletions in system catalogs (see CacheInvalidateHeapTuple).
34
34
* An update can generate two inval events, one for the old tuple and one for
35
35
* the new, but this is reduced to one event if the tuple's hash key doesn't
38
38
* hash key, there is a small risk of unnecessary invalidations due to chance