| 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-02 03:15:59 |
| Message-ID: | 1306744.1788318959@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 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. 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zexin Li | 2026-09-02 06:28:46 | Re: BUG #19645: Partition key opclass bypasses nondeterministic collation check, wrong results |
| Previous Message | Fujii Masao | 2026-09-02 03:08:30 | Re: BUG #19644: byteaout, float8out and float4out are marked IMMUTABLE but depend on GUCs |