aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/parse_expr.c
diff options
context:
space:
mode:
authorAlvaro Herrera <alvherre@alvh.no-ip.org>2020-10-20 19:22:09 -0300
committerAlvaro Herrera <alvherre@alvh.no-ip.org>2020-10-20 19:22:09 -0300
commitbbb927b4db9b3b449ccd0f76c1296de382a2f0c1 (patch)
tree067f24d5875ffd4f02968d69d2ef02af9bfffd9b /src/backend/parser/parse_expr.c
parent03d51b776d88badbeb4452c1ab452feb78dce36a (diff)
downloadpostgresql-bbb927b4db9b3b449ccd0f76c1296de382a2f0c1.tar.gz
postgresql-bbb927b4db9b3b449ccd0f76c1296de382a2f0c1.zip
Fix ALTER TABLE .. ENABLE/DISABLE TRIGGER recursion
More precisely, correctly handle the ONLY flag indicating not to recurse. This was implemented in 86f575948c77 by recursing in trigger.c, but that's the wrong place; use ATSimpleRecursion instead, which behaves properly. However, because legacy inheritance has never recursed in that situation, make sure to do that only for new-style partitioning. I noticed this problem while testing a fix for another bug in the vicinity. This has been wrong all along, so backpatch to 11. Discussion: https://postgr.es/m/20201016235925.GA29829@alvherre.pgsql
Diffstat (limited to 'src/backend/parser/parse_expr.c')
0 files changed, 0 insertions, 0 deletions