| From: | shihao zhong <zhong950419(at)gmail(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Staroverov Ilja <i(dot)staroverov(at)ftdata(dot)ru>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(at)eisentraut(dot)org>, "jj-zhang25(at)mails(dot)tsinghua(dot)edu(dot)cn" <jj-zhang25(at)mails(dot)tsinghua(dot)edu(dot)cn>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <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-11-08 01:30:18 |
| Message-ID: | CAGRkXqT7K5kON22t=JeDXdWz3wDqxiAhNLsJNJT-AZ-zryteJA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi Fujii-san,
I was worried this could break pg_upgrade.
With CREATE INDEX ix ON b ((v::text)) on 18, pg_upgrade --check passes,
but the upgrade to master fails:
ERROR: functions in index expression must be marked IMMUTABLE
I started [1] to track this kind of --check gap.
[1]
https://postgr.es/m/CAGRkXqRzM-68S9OhtLsTscZ_hhpHhy=ArWCdmp5GxRxo+UBmig@mail.gmail.com
Thanks,
Shihao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shihao zhong | 2026-11-08 02:18:52 | Re: set_config(‘search_path’) does not truncate names over 63 bytes, unlike SET |
| Previous Message | shihao zhong | 2026-11-08 01:15:45 | Re: BUG #19817: CREATE UNIQUE INDEX on a partitioned table can silently attach an invalid, not-ready child index, le |