Re: BUG #15053: SIGSEGV - While executing query with cube agregator

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: obeltrame(at)callixbrasil(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15053: SIGSEGV - While executing query with cube agregator
Date: 2018-02-06 19:19:40
Message-ID: 23669.1517944780@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

=?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:

> 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andreas Seltenreich 2018-02-06 22:00:47 Re: BUG #15053: SIGSEGV - While executing query with cube agregator
Previous Message PG Bug reporting form 2018-02-06 17:33:07 BUG #15053: SIGSEGV - While executing query with cube agregator