Re: ExecTypeSetColNames is fundamentally broken - Mailing list pgsql-hackers

From Robert Haas
Subject Re: ExecTypeSetColNames is fundamentally broken
Date
Msg-id CA+TgmoaYDAqLLmxo_d9h2SZ1Mw28M9w5QZMuZcaL6D2JdG_B6w@mail.gmail.com
Whole thread Raw
In response to ExecTypeSetColNames is fundamentally broken  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: ExecTypeSetColNames is fundamentally broken
List pgsql-hackers
On Sun, Dec 5, 2021 at 1:46 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> So 0001 attached fixes this by revoking the decision to apply
> ExecTypeSetColNames in cases where a Var or RowExpr is declared
> to return a named composite type.  This causes a couple of regression
> test results to change, but they are ones that were specifically
> added to exercise this behavior that we now see to be invalid.

I don't understand the code so I can't comment on the code, but I find
the regression test changes pretty suspect. Attaching any alias list
to the RTE ought to rename the output columns for all purposes, not
just the ones we as implementers find convenient. I understand that we
have to do *something* here and that the present behavior is buggy and
unacceptable ... but I'm not sure I accept that the only possible fix
is the one you propose here.

-- 
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Why doesn't pgstat_report_analyze() focus on not-all-visible-page dead tuple counts, specifically?
Next
From: Robert Haas
Date:
Subject: Re: pg_dump versus ancient server versions