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

From: Andrey Rachitskiy <pl0h0yp1(at)gmail(dot)com>
To: Amit Langote <amitlangote09(at)gmail(dot)com>
Cc: jian he <jian(dot)universality(at)gmail(dot)com>, zengman <zengman(at)halodbtech(dot)com>, syzhong16 <syzhong16(at)gmail(dot)com>, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #19621: Unexpected results of JSON_VALUE with DEFAULT ON EMPTY
Date: 2026-11-04 16:28:56
Message-ID: CAB8bMit6u2dKN77+WTeLCdB09VYSxagLfPi+RvRL44iZcvGB3w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

ср, 4 нояб. 2026 г., 15:06 Amit Langote <amitlangote09(at)gmail(dot)com>:

>
> Here is v4 with some comment and commit message updates, plus one more
> regression case for JSON_EXISTS’s default FALSE ON ERROR. I plan to
> commit and back-patch it to 17 barring objections.
>

Hi Amit,

LGTM

Thanks for the review

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message shihao zhong 2026-11-04 21:05:33 Re: set_config(‘search_path’) does not truncate names over 63 bytes, unlike SET
Previous Message Ayush Tiwari 2026-11-04 15:58:47 Re: BUG #19603: Vuln47: distance_taxicab and distance_chebyshev silently return 0 instead of NaN when a cube coordin