Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY

вт, 18 авг. 2026 г. в 13:56, Andrey Rachitskiy <pl0h0yp1(at)gmail(dot)com>:

>
> вт, 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.
>
>
Dear Amit,

Attached is v2 of the patch.
v1 was a malformed unified diff: three context lines after the
ExecEvalJsonIsPredicate hunk were missing the leading space, so
git apply rejected the file as corrupt. There is no code change
versus v1.

I also re-checked the reporter's JSON_EXISTS / JSON_VALUE /
JSON_QUERY examples from the later duplicate report [0]; they pass
with this patch.

[0]
https://www.postgresql.org/message-id/19654-3acd06154d027634@postgresql.org

--
Regards,
Rachitskiy Andrey