From: Tom Lane <tgl@sss.pgh.pa.us>
To: obeltrame@callixbrasil.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15053: SIGSEGV - While executing query with cube agregator
In-reply-to: <151793838713.1243.5246278119990227987@wrigleys.postgresql.org>
References: <151793838713.1243.5246278119990227987@wrigleys.postgresql.org>
Comments: In-reply-to =?utf-8?q?PG_Bug_reporting_form?=
 <noreply@postgresql.org>
	message dated "Tue, 06 Feb 2018 17:33:07 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <23668.1517944780.1@sss.pgh.pa.us>
Date: Tue, 06 Feb 2018 14:19:40 -0500
Message-ID: <23669.1517944780@sss.pgh.pa.us>
Precedence: bulk

=?utf-8?q?PG_Bug_reporting_form?= <noreply@postgresql.org> writes:
> the following postgres crash was generated during the execution of this
> query:

>  select
>   freeswitch_bug_events.created_at::date,
>   freeswitch_nodes."name",
>   tenants."name",
>   count(*) filter(where freeswitch_bug_events.event = 'call received'),
>   count(*) filter(where freeswitch_bug_events.event = 'status changed')
> from dev.freeswitch_bug_events
>   join public.tenants on freeswitch_bug_events.tenant = tenants.id 
>   join public.freeswitch_nodes on freeswitch_bug_events.node =
> freeswitch_nodes.id
> group by 
>   cube (freeswitch_bug_events.created_at::date, freeswitch_nodes."name",
> tenants."name" )

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.)

If not, please see if you can extract a self-contained test case.  That
stack trace is not really enough information to fix it.

			regards, tom lane