Re: Server process exited with status 139 (meaning?) - Mailing list pgsql-hackers

From Ed Loehr
Subject Re: Server process exited with status 139 (meaning?)
Date
Msg-id 3956E936.E87CA36D@austin.rr.com
Whole thread Raw
In response to Re: Server process exited with status 139 (meaning?)  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Tom Lane wrote:
> 
> Ed Loehr <eloehr@austin.rr.com> writes:
> > I don't need help on this as I found workable queries for my purposes,
> > but here is a simplified core-dumper (7.0beta3) for posterity...
> 
> This doesn't come close to doing anything as-is, but even reading
> between the lines ("activity"=>"bar" etc) and deleting references
> to missing fields, I can't get a crash.  Possibly a bug fixed since
> beta3?

I'll assume you tried my latest typo-free version on an HP box after
posting this and got the same results (i.e., nothing).  Maybe someone
else would care to verify on a Linux box?  I'm on RH 6.2 with dual
PIII's...

Regards,
Ed Loehr


pgsql-hackers by date:

Previous
From: Ed Loehr
Date:
Subject: ExecInitIndexScan: both left and right ops are rel-vars
Next
From: Ed Loehr
Date:
Subject: Re: ExecInitIndexScan: both left and right ops are rel-vars