| From: | Andrey Rachitskiy <pl0h0yp1(at)gmail(dot)com> |
|---|---|
| To: | zengman <zengman(at)halodbtech(dot)com> |
| Cc: | syzhong16 <syzhong16(at)gmail(dot)com>, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Amit Langote <amitlangote09(at)gmail(dot)com> |
| Subject: | Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY |
| Date: | 2026-08-18 08:56:07 |
| Message-ID: | CAB8bMitKaUUXy0dnBCpn_Q62ONOtK+CWetOdmMsbOYFrGa7nOA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
вт, 18 авг. 2026 г. в 07:06, zengman <zengman(at)halodbtech(dot)com>:
> I tested the current patch, but it does not seem to address the problem I
> reported here:
> ```
>
> https://www.postgresql.org/message-id/19625-683b498c92087bc8%40postgresql.org
> ```
>
Dear Zeng,
One is per-row executor state. The other is a wrong parse-time rewrite of a
boolean DEFAULT. They share only that both involve SQL/JSON DEFAULT.
Combining them would mix an executor opcode change with a parser coercion
change, and it would make review and back-patching harder.
--
Regards,
Rachitskiy Andrey
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2026-08-18 09:33:12 | BUG #19627: 32,768 trigger arguments wrap `tgnargs` and are silently lost at runtime |
| Previous Message | Andrey Rachitskiy | 2026-08-18 08:29:19 | Re: BUG #19616: pgoutput sends stream abort ('A') to clients that did not enable streaming |