Re: BUG #19644: byteaout, float8out and float4out are marked IMMUTABLE but depend on GUCs

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: jj-zhang25(at)mails(dot)tsinghua(dot)edu(dot)cn, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19644: byteaout, float8out and float4out are marked IMMUTABLE but depend on GUCs
Date: 2026-09-04 17:27:19
Message-ID: 1577102.1788542839@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Fujii Masao <masao(dot)fujii(at)gmail(dot)com> writes:
> On Wed, Sep 2, 2026 at 12:15 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Richard Guo 2026-09-04 23:09:42 Re: BUG #19653: "variable not found in subplan target list" during planning with parallel parameterized nested loop,
Previous Message Andrey Rachitskiy 2026-09-04 16:10:50 Re: BUG #19649: Qual pushdown into GROUP BY subqueries ignores non-equivalence-preserving references to grouping col