Skip site navigation (1) Skip section navigation (2)

Re: Server process exited with status 139

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: jyoung(at)conservatives(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Server process exited with status 139
Date: 2001-02-13 15:31:03
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
pgsql-bugs(at)postgresql(dot)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

In response to

pgsql-bugs by date

Next:From: pgsql-bugsDate: 2001-02-13 17:32:53
Subject: PgSQL 7.1 beta 3 breaks ODBC
Previous:From: pgsql-bugsDate: 2001-02-13 10:54:42
Subject: Server process exited with status 139

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group