Fix use of relcache TriggerDesc field introduced by commit 05c8482f7f. The commit added code which used a relcache TriggerDesc field across another cache access, which it shouldn't because the relcache doesn't guarantee it won't get moved.
Diagnosed-by: Tom Lane Author: Greg Nancarrow Reviewed-by: Hou Zhijie, Amit Kapila Discussion: https://postgr.es/m/[email protected] Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/e2cda3c20a61c76e497fb2ebb6d2b2ae8c43c014 Modified Files -------------- src/backend/optimizer/util/clauses.c | 24 +++++++++++++++--------- 1 file changed, 15 insertions(+), 9 deletions(-)
