Postgres Pro
Downloads
Home   >   mailing lists

Re: error status 139 - Mailing list pgsql-admin

From Tom Lane
Subject Re: error status 139
Date
Msg-id 6901.995690204@sss.pgh.pa.us
Whole thread Raw
In response to error status 139  (Laurette Cisneros <laurette@nextbus.com>)
Responses Better copy/import
Re: error status 139
Re: error status 139
Re: error status 139
List pgsql-admin
Tree view 
Laurette Cisneros <laurette@nextbus.com> writes:
> Any idea what status 139 indicates?

SIGSEGV core dump, on most systems.  Look for the backend core file
(in $PGDATA/base/yourdb/core) and send us a gdb stack trace ...
also, it would help to know what PG version you are running, on
what platform, and what you were doing when the crash happened.

            regards, tom lane

pgsql-admin by date:

Previous
From: Laurette Cisneros
Date:
Subject: error status 139
Next
From: Tim Boring
Date:
Subject: destroydb: command not found