diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2012-03-07 14:51:13 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2012-03-07 14:51:13 -0500 |
commit | d4bf3c9c94305e692349fb6fe0c67e483b72ae87 (patch) | |
tree | f8b6fb180e026683ad7a06ab723e98eb86986c9d /src/backend/access/gist | |
parent | e685a8e6651b0e55996e6eba6917302607866793 (diff) | |
download | postgresql-d4bf3c9c94305e692349fb6fe0c67e483b72ae87.tar.gz postgresql-d4bf3c9c94305e692349fb6fe0c67e483b72ae87.zip |
Expose an API for calculating catcache hash values.
Now that cache invalidation callbacks get only a hash value, and not a
tuple TID (per commits 632ae6829f7abda34e15082c91d9dfb3fc0f298b and
b5282aa893e565b7844f8237462cb843438cdd5e), 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.
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions