Re: Backend crash with user defined aggregate

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Backend crash with user defined aggregate
Date: 2005-09-24 16:30:19
Message-ID: 13292.1127579419@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com> writes:
> Fails the same way in each case. It was doing a HashAggregate last time; but
> I just reproduced it now with a GroupAggregate.

> fli=# explain analyze select ext_doc_id,strcat_agg(nam)||+strcat_agg(val) from facet_raw group by ext_doc_id;
> FATAL: terminating connection due to administrator command

Hmm. Now that I look at it again, that message implies that something
sent SIGTERM to the backend. You need to figure out where that signal
is coming from and why. I think I have heard of platforms on which
SIGTERM is generated if a process exceeds a preset run-time limit;
is it possible that you've started your postmaster with finite limits
on process runtime? What is the platform exactly, anyway?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2005-09-24 16:55:36 Re: Extraordinarily slow!!
Previous Message Tom Lane 2005-09-24 16:15:53 Re: Problems creating view