mirror of https://github.com/postgres/postgres
Now that cache invalidation callbacks get only a hash value, and not a tuple TID (per commitspull/3/head632ae6829f
andb5282aa893
), the only way they can restrict what they invalidate is to know what the hash values mean. setrefs.c was doing this via a hard-wired assumption but that seems pretty grotty, and it'll only get worse as more cases come up. So let's expose a calculation function that takes the same parameters as SearchSysCache. Per complaint from Marko Kreen.
parent
e685a8e665
commit
d4bf3c9c94
Loading…
Reference in new issue