Re: BUG #19644: byteaout, float8out and float4out are marked IMMUTABLE but depend on GUCs - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #19644: byteaout, float8out and float4out are marked IMMUTABLE but depend on GUCs
Date
Msg-id 1577102.1788542839@sss.pgh.pa.us
Whole thread
In response to BUG #19644: byteaout, float8out and float4out are marked IMMUTABLE but depend on GUCs  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
Fujii Masao <masao.fujii@gmail.com> writes:
> On Wed, Sep 2, 2026 at 12:15 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I agree with changing this on master, but I see no reason to do
>> anything whatever in the back branches.

> +1. BTW, what about v19? Since it hasn't been released yet, it's OK to
> make this change there, or it's too late even for v19?

It's been wrong for so long that I'm not that rushed to fix it in 19.
We might find that there are consequences to be dealt with, so better
to let the fix settle in master.

> On further review, point_out, ISTM that lseg_out, path_out, box_out, poly_out,
> circle_out, and line_out are marked IMMUTABLE but depend on extra_float_digits.
> Similarly, pg_mcv_list_out is marked IMMUTABLE but depends on bytea_output.
> Perhaps we should fix these at the same time...

Agreed.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #19653: "variable not found in subplan target list" during planning with parallel parameterized nested loop,
Next
From: Richard Guo
Date:
Subject: Re: BUG #19653: "variable not found in subplan target list" during planning with parallel parameterized nested loop,