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

From: zengman <zengman(at)halodbtech(dot)com>
To: Andrey Rachitskiy <pl0h0yp1(at)gmail(dot)com>, syzhong16 <syzhong16(at)gmail(dot)com>, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Cc: Amit Langote <amitlangote09(at)gmail(dot)com>
Subject: Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
Date: 2026-08-18 02:06:15
Message-ID: tencent_3BDE4F7404C05A9C7D71602A@qq.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi everyone,

I have another question related to JSON functions. Although it is a different issue, I wonder whether it would make sense to handle both cases in the same patch.

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
```

--
Regards,
Man Zeng

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2026-08-18 03:06:09 BUG #19626: Segmentation fault planning self-join IN subquery with LATERAL UNION ALL
Previous Message Dan Stefura 2026-08-17 21:45:22 B-tree index scan ~2x slower on PG18 vs PG17 for skewed equality-prefix + range-condition lookups, with essentially the same plan