Re: Server process exited with status 139 - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Server process exited with status 139
Date
Msg-id 4588.982078263@sss.pgh.pa.us
Whole thread Raw
In response to Server process exited with status 139  (pgsql-bugs@postgresql.org)
List pgsql-bugs
pgsql-bugs@postgresql.org writes:
> I am consistently getting "Server process exited with status 139"
> whilst trying to create a straightforward index - "Create index test1
> on voter(name);"

Hm.  I wonder if the table contains any corrupted data.  If you do
something else that scans all the name entries, does it work?  One
simple test would be SELECT max(name) FROM voter.

> Do you think I simply don't have enough memory?

No, it's corrupted data of some sort ... need to figure out what's
inducing that ...

            regards, tom lane

pgsql-bugs by date:

Previous
From: pgsql-bugs@postgresql.org
Date:
Subject: Server process exited with status 139
Next
From: pgsql-bugs@postgresql.org
Date:
Subject: PgSQL 7.1 beta 3 breaks ODBC