Re: signal 11

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Tanya Mamedalin" <tmamedalin(at)registrypro(dot)pro>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: signal 11
Date: 2004-01-26 16:58:30
Message-ID: 8333.1075136310@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Tanya Mamedalin" <tmamedalin(at)registrypro(dot)pro> writes:
> Possible ways to reproduce the error: Run a multipart query similar to:

> SELECT DISTINCT o.outage_id, o.machine, o.service, o.level, o.comments,
> o2.time, e.num
> FROM outages o, outages o2, escalation e
> WHERE o.outage_id='31009'
> AND e.pathname = (SELECT pathname from escalation_link el
> WHERE el.machine=o.machine AND el.service=o.service)
> AND e.level=o.level
> AND o2.outage_id=o.outage_id
> AND o2.status in ('ALERT','WARN','CRIT','DOWN','UNKNOWN')
> ORDER BY LEVEL DESC LIMIT 1;

This is difficult to do when you have not offered the definitions of the
tables used by the query ...

regards, tom lane

In response to

  • signal 11 at 2004-01-23 16:30:53 from Tanya Mamedalin

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2004-01-26 17:00:28 Re: 7.4.xx regression
Previous Message Tom Lane 2004-01-26 16:55:26 Re: connection handling in 7.4.1