Re: array_agg(DISTINCT) caused a segmentation fault

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: array_agg(DISTINCT) caused a segmentation fault
Date: 2023-02-13 07:44:02
Message-ID: CAApHDvrWu0G1caebi21=pELRtpcyu+1sDvo_c-vkogYJ=tQrvA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, 13 Feb 2023 at 18:29, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> wrote:
> =# SELECT array_agg(distinct val) FROM (SELECT NULL AS val FROM generate_series(1, 2)) hoge;
> LOG: server process (PID 76507) was terminated by signal 11: Segmentation fault: 11
> DETAIL: Failed process was running: SELECT array_agg(distinct val) FROM (SELECT NULL AS val FROM generate_series(1, 2)) hoge;

This was a fairly trivial logic bug in
ExecEvalPreOrderedDistinctSingle(). The JIT code calls that same
function and ExecEvalPreOrderedDistinctMulti() uses the standard
expression evaluation logic. So looks like the problem is just
isolated to ExecEvalPreOrderedDistinctSingle().

I've now pushed a fix for it and included your test. To get it to
crash it needed to be a byref aggregate without a strict transition
function. There are not too many of those, which is probably why
nobody noticed this before.

David

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Fujii Masao 2023-02-13 09:03:58 Re: array_agg(DISTINCT) caused a segmentation fault
Previous Message Kyotaro Horiguchi 2023-02-13 06:45:49 Re: WAL segments removed from primary despite the fact that logical replication slot needs it.