From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
Subject: | Re: ExecTypeSetColNames is fundamentally broken |
Date: | 2022-03-17 22:28:11 |
Message-ID: | 973180.1647556091@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Aleksander Alekseev <aleksander(at)timescale(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-03-17 22:33:38 | Re: [PATCH] Expose port->authn_id to extensions and triggers |
Previous Message | Jacob Champion | 2022-03-17 22:02:16 | Re: [PATCH] Expose port->authn_id to extensions and triggers |