Cache NO ACTION foreign keys separately from RESTRICT foreign keys Now that we generate different SQL for temporal NO ACTION vs RESTRICT foreign keys, we should cache their query plans with different keys. Since the key also includes the constraint oid, this shouldn't be necessary, but we have been seeing build farm failures that suggest we might be sometimes using a cached NO ACTION plan to implement a RESTRICT constraint.
Author: Paul A. Jungwirth <p...@illuminatedcomputing.com> Discussion: https://www.postgresql.org/message-id/flat/CA+renyUApHgSZF9-nd-a0+OPGharLQLO=mdhcy4_qq0+noc...@mail.gmail.com Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/9926f854d07784d72aada16c8038b558fbc45d13 Modified Files -------------- src/backend/utils/adt/ri_triggers.c | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-)
