Re: BUG #14344: string_agg(DISTINCT ..) crash

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Regina Obe <lr(at)pcorp(dot)us>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14344: string_agg(DISTINCT ..) crash
Date: 2016-10-18 01:29:10
Message-ID: CAM3SWZTa0rXKu-nZA3Jg3xn6v88apY2=SrYdBgC5ANj_XhRgxg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Oct 17, 2016 at 6:42 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> FWIW, I think this is an appropriate solution for 9.6, but I'd favor
> changing the function's API to be like tuplestore_gettupleslot's
> in HEAD.

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.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message digoal 2016-10-18 07:57:33 BUG #14378: when drop schema, standby will do many more than primary, and very slow, it's a bug?
Previous Message Michael Paquier 2016-10-18 00:01:43 Re: BUG #14376: How stop/cancel/break/quit the "process watcher - restoring backup on the server"