| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
| Cc: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Making jsonb_agg() faster |
| Date: | 2025-12-13 21:25:50 |
| Message-ID: | 1361925.1765661150@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> Alexander Lakhin <exclusion(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chao Li | 2025-12-13 23:22:28 | Re: Small patch to improve safety of utf8_to_unicode(). |
| Previous Message | Peter Eisentraut | 2025-12-13 19:57:56 | Re: SQL Property Graph Queries (SQL/PGQ) |