| From: | Andreas Seltenreich <andreas(dot)seltenreich(at)credativ(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | obeltrame(at)callixbrasil(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15053: SIGSEGV - While executing query with cube agregator |
| Date: | 2018-02-06 22:00:47 |
| Message-ID: | 87wozpye0g.fsf@credativ.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Tom Lane writes:
> =?utf-8?q?PG_Bug_reporting_form?= <noreply(at)postgresql(dot)org> writes:
>> the following postgres crash was generated during the execution of this
>> query:
[...]
>> group by cube
>
> Hmm, well, first please update to something newer than 9.6.3, to see if
> the problem is already resolved. (9.6.7 is being released this week.)
backtrace and query look similar to the issue we reported leading to the
following commitfest entry:
https://commitfest.postgresql.org/16/1413/
Our customer hasn't seen any crashes with cube() statements since
setting
replacement_sort_tuples = 0
I'm afraid this workaround might be needed here as well unless a fix
makes it into 9.6.7.
regards,
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2018-02-06 22:14:40 | Re: BUG #15053: SIGSEGV - While executing query with cube agregator |
| Previous Message | Tom Lane | 2018-02-06 19:19:40 | Re: BUG #15053: SIGSEGV - While executing query with cube agregator |