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

On Wed, Sep 2, 2026 at 12:15 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Fujii Masao <masao(dot)fujii(at)gmail(dot)com> writes:
> > On Tue, Sep 1, 2026 at 10:12 PM PG Bug reporting form
> > <noreply(at)postgresql(dot)org> wrote:
> >> Mark byteaout, float8out and float4out (and the corresponding casts to text)
> >> STABLE rather than IMMUTABLE, matching date_out, interval_out and cash_out.
>
> > +1 to making such changes on master, even though they would cause
> > several compatibility issues for existing users...
>
> 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?

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...

Regards,

--
Fujii Masao