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

From Peter Eisentraut
Subject Re: Server process exited with status 139 (meaning?)
Date
Msg-id Pine.LNX.4.21.0006241904051.348-100000@localhost.localdomain
Whole thread Raw
In response to Server process exited with status 139 (meaning?)  (Ed Loehr <eloehr@austin.rr.com>)
List pgsql-hackers
Ed Loehr writes:

> I have a query crashing the backend and leaving this message in the
> server log...
> What does exit status 139 mean?

The backend terminated because of a segmentation fault (note 139 = 128 +
11, 11 = SIGSEGV). So it's definitely a bug and we'd need to see the
query.

> Better still would be a pointer to some documentation for error codes
> if such beast exists...

See wait(2). Of course we could also make the error message more
expressive.

-- 
Peter Eisentraut                  Sernanders väg 10:115
peter_e@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Big 7.1 open items
Next
From: Tom Lane
Date:
Subject: Re: 64-bit sequences