Re: BUG #14344: string_agg(DISTINCT ..) crash - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: BUG #14344: string_agg(DISTINCT ..) crash
Date
Msg-id CAM3SWZTaXr-XcoMS0Nmmf8LHuctyUER50vZh7q5SgP6xuHjS8A@mail.gmail.com
Whole thread Raw
In response to Re: BUG #14344: string_agg(DISTINCT ..) crash  (Peter Geoghegan <pg@heroku.com>)
List pgsql-bugs
On Mon, Oct 17, 2016 at 6:29 PM, Peter Geoghegan <pg@heroku.com> wrote:
> In light of the fact that the minimal fix has low overhead, I agree.
> I've drafted a patch to do this. I expect to be able to post it in the
> next few days.

I've put this off until I can get some buy-in from Heikki about a more
general issue with "should_free" arguments in tuplesort.c [1].

[1] https://www.postgresql.org/message-id/CAM3SWZQWZZ_N=DmmL7tKy_OUjGH_5mN=N=A6h7kHyyDvEhg2DA@mail.gmail.com
--
Peter Geoghegan

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Compilation of timezone source with zic fails (on mountpoint)
Next
From: James Parks
Date:
Subject: AfterTriggerSaveEvent() Error on altered foreign key cascaded delete