| From: | jian he <jian(dot)universality(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: json/jsonb cleanup + FmgrInfo caching |
| Date: | 2026-10-13 08:23:26 |
| Message-ID: | CACJufxF4yYQsTavPHkfyHRFvh1rO7xWH39u9pRJ9FGi5Wb_j9Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jul 3, 2026 at 12:25 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> 0002 fixes the bug discovered during the development of 0001 by
> removing the special case. AFAICT, the anyarray and anycompatiblearray
> cases are unreachable, but the record case is reachable, and the
> included test case shows how this could hypothetically matter. It
> seems unlikely we'll inconvenience any significant number of users by
> changing this, but in theory somebody's upgrade could fail.
>
Hi.
Shihao Zhong [1] direct me to here.
json_check_mutability was changed in PG19, and in 0001 you removed the
call to json_categorize_type from json_check_mutability. We can use that
portion for PG19, and the json_categorize_type refactoring can go to PG20.
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Don-t-treat-record-json-b-conversions-as-immutable.txt | text/plain | 14.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nazir Bilal Yavuz | 2026-10-13 08:30:57 | Re: New test function replace_conf() to get rid of unlink/append pattern |
| Previous Message | Amit Langote | 2026-10-13 08:14:47 | Re: ERROR: SubPlan found with no parent plan |