aboutsummaryrefslogtreecommitdiff
path: root/contrib/jsonb_plperl/jsonb_plperl.c
diff options
context:
space:
mode:
authorAlexander Korotkov <akorotkov@postgresql.org>2024-10-24 14:35:52 +0300
committerAlexander Korotkov <akorotkov@postgresql.org>2024-10-24 14:35:52 +0300
commitb85a9d046efdd27775cbe7db9e92aad96aab4ada (patch)
tree63f9cb3fafa222f54c3e0e0342ff0b8a6d2eb501 /contrib/jsonb_plperl/jsonb_plperl.c
parentc1500a1ba7e16ac9e98c6baf792f0be64a48e839 (diff)
downloadpostgresql-b85a9d046efdd27775cbe7db9e92aad96aab4ada.tar.gz
postgresql-b85a9d046efdd27775cbe7db9e92aad96aab4ada.zip
Avoid looping over all type cache entries in TypeCacheRelCallback()
Currently, when a single relcache entry gets invalidated, TypeCacheRelCallback() has to loop over all type cache entries to find appropriate typentry to invalidate. Unfortunately, using the syscache here is impossible, because this callback could be called outside a transaction and this makes impossible catalog lookups. This is why present commit introduces RelIdToTypeIdCacheHash to map relation OID to its composite type OID. We are keeping RelIdToTypeIdCacheHash entry while corresponding type cache entry have something to clean. Therefore, RelIdToTypeIdCacheHash shouldn't get bloat in the case of temporary tables flood. There are many places in lookup_type_cache() where syscache invalidation, user interruption, or even error could occur. In order to handle this, we keep an array of in-progress type cache entries. In the case of lookup_type_cache() interruption this array is processed to keep RelIdToTypeIdCacheHash in a consistent state. Discussion: https://postgr.es/m/5812a6e5-68ae-4d84-9d85-b443176966a1%40sigaev.ru Author: Teodor Sigaev Reviewed-by: Aleksander Alekseev, Tom Lane, Michael Paquier, Roman Zharkov Reviewed-by: Andrei Lepikhov, Pavel Borisov, Jian He, Alexander Lakhin Reviewed-by: Artur Zakirov
Diffstat (limited to 'contrib/jsonb_plperl/jsonb_plperl.c')
0 files changed, 0 insertions, 0 deletions