Thread: pgsql: Flush relcache entries when their FKs are meddled with
Flush relcache entries when their FKs are meddled with Back in commit 100340e2dcd0, we made relcache entries keep lists of the foreign keys applying to the relation -- but we forgot to update CacheInvalidateHeapTuple to flush those entries when new FKs got created or existing ones updated/deleted. No bugs appear to have been reported that would be explained by this ommission, but I noticed the problem while working on an unrelated bugfix which clearly showed it. Fix by adding relcache flush on relevant foreign key changes. Backpatch to 9.6, like the aforementioned commit. Discussion: https://postgr.es/m/201901211927.7mmhschxlejh@alvherre.pgsql Reviewed-by: Tom Lane Branch ------ REL_10_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/3037b28b89b44fccfcfddb2254655f45b3005f82 Modified Files -------------- src/backend/utils/cache/inval.c | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+)