From: Tom Lane <tgl@sss.pgh.pa.us>
To: Fujii Masao <masao.fujii@gmail.com>
Cc: jj-zhang25@mails.tsinghua.edu.cn
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19644: byteaout, float8out and float4out are marked IMMUTABLE but depend on GUCs
Date: Tue, 01 Sep 2026 23:15:59 -0400
Message-ID: <1306744.1788318959@sss.pgh.pa.us> (raw)
In-Reply-To: <CAHGQGwFPDZ8bMW6adGtAiEmMWQ8hTPCV_1APtoTQ38+2bXXgWA@mail.gmail.com>
References: <19644-d6db3fb5e5ad92f4@postgresql.org>
<CAHGQGwFPDZ8bMW6adGtAiEmMWQ8hTPCV_1APtoTQ38+2bXXgWA@mail.gmail.com>
Fujii Masao <masao.fujii@gmail.com> writes:
> On Tue, Sep 1, 2026 at 10:12 PM PG Bug reporting form
> <noreply@postgresql.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. There are few situations
where the mutability marking of a datatype output function matters,
and even if it does, you don't see an actual problem unless you
change one of these GUCs mid-query. If it were a big deal,
we would have noticed this ages ago.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, masao.fujii@gmail.com, jj-zhang25@mails.tsinghua.edu.cn, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19644: byteaout, float8out and float4out are marked IMMUTABLE but depend on GUCs
In-Reply-To: <1306744.1788318959@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox