| From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Andreas Seltenreich <andreas(dot)seltenreich(at)credativ(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, obeltrame(at)callixbrasil(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15053: SIGSEGV - While executing query with cube agregator |
| Date: | 2018-02-07 11:24:54 |
| Message-ID: | 878tc5t5h1.fsf@news-spur.riddles.org.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
>>>>> "Peter" == Peter Geoghegan <pg(at)bowt(dot)ie> writes:
> On Tue, Feb 6, 2018 at 2:00 PM, Andreas Seltenreich
> <andreas(dot)seltenreich(at)credativ(dot)de> wrote:
>> backtrace and query look similar to the issue we reported leading to the
>> following commitfest entry:
>>
>> https://commitfest.postgresql.org/16/1413/
Peter> I suspect the same.
I just eyeballed that. The obvious question that comes to mind is, can't
this issue be fixed in nodeAgg rather than monkeying with the slot code?
--
Andrew (irc:RhodiumToad)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2018-02-07 14:42:22 | BUG #15054: intermittent error: An I/O error occured while sending to the backend. |
| Previous Message | Greg Clough | 2018-02-07 10:41:36 | RE: BUG #15052: unresponsive client |