From: Andreas Seltenreich <andreas.seltenreich@credativ.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: obeltrame@callixbrasil.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15053: SIGSEGV - While executing query with cube agregator
Date: Tue, 06 Feb 2018 23:00:47 +0100
Message-ID: <87wozpye0g.fsf@credativ.de> (raw)
In-Reply-To: <23669.1517944780@sss.pgh.pa.us>
References: <151793838713.1243.5246278119990227987@wrigleys.postgresql.org>
<23669.1517944780@sss.pgh.pa.us>
Tom Lane writes:
> =?utf-8?q?PG_Bug_reporting_form?= <noreply@postgresql.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: andreas.seltenreich@credativ.de, tgl@sss.pgh.pa.us, obeltrame@callixbrasil.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15053: SIGSEGV - While executing query with cube agregator
In-Reply-To: <87wozpye0g.fsf@credativ.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox