[9.2] Confusion over CacheRegisterSyscacheCallback
От
Marko Kreen
Тема
[9.2] Confusion over CacheRegisterSyscacheCallback
Дата
Msg-id
20120306153331.GA11164@gmail.com
Список
Дерево обсуждения
[9.2] Confusion over CacheRegisterSyscacheCallback Marko Kreen <markokr@gmail.com>
Re: [9.2] Confusion over CacheRegisterSyscacheCallback Tom Lane <tgl@sss.pgh.pa.us>
Re: [9.2] Confusion over CacheRegisterSyscacheCallback Marko Kreen <markokr@gmail.com>
Re: [9.2] Confusion over CacheRegisterSyscacheCallback Tom Lane <tgl@sss.pgh.pa.us>
Re: [9.2] Confusion over CacheRegisterSyscacheCallback Marko Kreen <markokr@gmail.com>
Re: [9.2] Confusion over CacheRegisterSyscacheCallback Tom Lane <tgl@sss.pgh.pa.us>
Re: [9.2] Confusion over CacheRegisterSyscacheCallback Marko Kreen <markokr@gmail.com>
Commit b5282aa893: "Revise sinval code to remove no-longer-used tuple TID from inval messages." dropped ItemPointer from callbacks and replaced it with "hashValue". There seems to be 2 ways that new backend code calculates it: - hashoid(oid), which seems to assume too much? - CatalogCacheComputeTupleHashValue(), which is 'static'. So my question is that after doing generic SearchSysCache() like: tup = SearchSysCache(USERMAPPINGUSERSERVER, ObjectIdGetDatum(user_mapping->userid), ObjectIdGetDatum(foreign_server->serverid), 0, 0); what is the proper way to calculate the hashValue that will be given to callback? -- marko
В списке pgsql-hackers по дате отправления
От: Pavel Stehule
Дата: