Re: pg_get_viewdef() produces non-round-trippable SQL for views with USING join on mismatched integer types
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Richard Guo <guofenglinux@gmail.com>
Cc: Swirl Smog Dowry <swirl-smog-dowry@duck.com>,
pgsql-bugs@lists.postgresql.org
Date: 2026-02-27T18:08:36Z
Lists: pgsql-bugs
I wrote: > Richard Guo <guofenglinux@gmail.com> writes: >> I am on the fence about whether this fix is safe to back-patch to v18. > I don't think we have a lot of choice. The cases where it makes a > difference are pretty broken. Fortunately, I think these cases > are rare. JOIN USING combining two different-type columns has got > to be an edge-case usage, and I think it likely doesn't matter much > in other cases. I spent a bit of effort on determining which cases actually cause wrong output, and AFAICT it's very narrow: you need "SELECT ... t1 LEFT JOIN t2 USING (x) GROUP BY x" where t1.x and t2.x are different data types and t1.x is the side requiring coercion. With no coercion, or if the join side to be coerced is nullable, we show the flattened alias Var but that doesn't actually break anything. So I went ahead and pushed this, using your test case. regards, tom lane
Commits
-
Don't flatten join alias Vars that are stored within a GROUP RTE.
- c2c1962a64b5 18.4 landed
- 98616ac18b49 19 (unreleased) landed
-
Introduce an RTE for the grouping step
- 247dea89f761 18.0 cited