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

From Tom Lane
Subject Re: ExecTypeSetColNames is fundamentally broken
Date
Msg-id 973180.1647556091@sss.pgh.pa.us
Whole thread Raw
In response to Re: ExecTypeSetColNames is fundamentally broken  (Aleksander Alekseev <aleksander@timescale.com>)
List pgsql-hackers
Aleksander Alekseev <aleksander@timescale.com> writes:
> I understand the concern expressed by Robert in respect of backward
> compatibility. From the user's perspective, personally I would prefer
> a fixed bug over backward compatibility. Especially if we consider the
> fact that the current behaviour of cases like `select row_to_json(i)
> from int8_tbl i(x,y)` is not necessarily the correct one, at least it
> doesn't look right to me.

It's debatable anyway.  I'd be less worried about changing this behavior
if we didn't have to back-patch it ... but I see no good alternative.

> So unless anyone has strong objections against the proposed fix or can
> propose a better patch, I would suggest merging it.

Done now.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: [PATCH] Expose port->authn_id to extensions and triggers
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] Expose port->authn_id to extensions and triggers