Prevent failure when RowExpr or XmlExpr is parse-analyzed twice. transformExpr() is required to cope with already-transformed expression trees, for various ugly-but-not-quite-worth-cleaning-up reasons. However, some of its newer subroutines hadn't gotten the memo. This accounts for bug #7763 from Norbert Buchmuller: transformRowExpr() was overwriting the previously determined type of a RowExpr during CREATE TABLE LIKE INCLUDING INDEXES. Additional investigation showed that transformXmlExpr had the same kind of problem, but all the other cases seem to be safe.
Andres Freund and Tom Lane Branch ------ REL8_3_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/4297f1732f7bf8f45f81a5e996d8333f2863a3d3 Modified Files -------------- src/backend/parser/gram.y | 3 +++ src/backend/parser/parse_expr.c | 19 +++++++++++++++++-- 2 files changed, 20 insertions(+), 2 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
