Fix use of relcache TriggerDesc field introduced by commit 05c8482f7f.
authorAmit Kapila <akapila@postgresql.org>
Fri, 12 Mar 2021 09:44:41 +0000 (15:14 +0530)
committerAmit Kapila <akapila@postgresql.org>
Fri, 12 Mar 2021 09:44:41 +0000 (15:14 +0530)
commite2cda3c20a61c76e497fb2ebb6d2b2ae8c43c014
treebc36e932c603b30cf13b3273acd988ea281d92e1
parent57dcc2ef3320de3e1aef6f668601e6ad2bdf88c4
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/2309260.1615485644@sss.pgh.pa.us
src/backend/optimizer/util/clauses.c