Request a Demo
Home   >   mailing lists

Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY - Mailing list pgsql-bugs

From Andrey Rachitskiy
Subject Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
Date
Msg-id CAB8bMitKaUUXy0dnBCpn_Q62ONOtK+CWetOdmMsbOYFrGa7nOA@mail.gmail.com
Whole thread
List pgsql-bugs
Tree view

вт, 18 авг. 2026 г. в 07:06, zengman <zengman@halodbtech.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

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #19626: Segmentation fault planning self-join IN subquery with LATERAL UNION ALL
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: BUG #19627: 32,768 trigger arguments wrap `tgnargs` and are silently lost at runtime