diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2020-01-01 19:31:41 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2020-01-01 19:31:41 -0500 |
| commit | 823e739d4a7257cf0ca58fc6eff3c4cec308fccf (patch) | |
| tree | 6cdf250633c6af2ec1904862aa3fed07ffadc328 /src/backend/parser/parse_target.c | |
| parent | c5f3b53b0ef2e8ae78e7488148c12bfe5939ca17 (diff) | |
| download | postgresql-823e739d4a7257cf0ca58fc6eff3c4cec308fccf.tar.gz postgresql-823e739d4a7257cf0ca58fc6eff3c4cec308fccf.zip | |
Test GROUP BY matching of join columns that are type-coerced by USING.
If we have, say, an int column that is left-joined to a bigint column
with USING, the merged column is the int column promoted to bigint.
GROUP BY's tests for whether grouping on the merged column allows a
reference to the underlying column, or vice versa, should know about
that relationship --- and they do. But I nearly broke this case with
an ill-advised optimization, so the lack of any test coverage for it
seems like a bad idea.
Diffstat (limited to 'src/backend/parser/parse_target.c')
0 files changed, 0 insertions, 0 deletions