Re: Making jsonb_agg() faster

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Alexander Lakhin <exclusion@gmail.com>

Cc: Chao Li <li.evan.chao@gmail.com>, jian he <jian.universality@gmail.com>, pgsql-hackers@lists.postgresql.org

Date: 2025-12-13T21:25:50Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix jsonb_object_agg crash after eliminating null-valued pairs.
- ef5f559b95e2 19 (unreleased) landed
Micro-optimize datatype conversions in datum_to_jsonb_internal.
- 005a2907dc30 19 (unreleased) landed
Remove fundamentally-redundant processing in jsonb_agg() et al.
- b61aa76e4585 19 (unreleased) landed
Revise APIs for pushJsonbValue() and associated routines.
- 0986e95161ce 19 (unreleased) landed
Add a macro for the declared typlen of type timetz.
- 3628af42107d 19 (unreleased) landed

I wrote:
> Alexander Lakhin <exclusion@gmail.com> writes:
>> I and SQLsmith have discovered that the following query:
>> select jsonb_object_agg_unique_strict(i, null) over (order by i) from
>>           (select i from generate_series(1, 20) g(i));
>> triggers SIGSEGV:

> Thanks for the report!  It seems to be specific to use as a window
> function; I see no problem without the OVER clause.  Will look closer
> later.

Fixed, thanks again for finding this.

			regards, tom lane