From: | "Maksim Likharev" <mlikharev(at)aurigin(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: PG crash on simple query |
Date: | 2003-07-02 00:28:59 |
Message-ID: | 56510AAEF435D240958D1CE8C6B1770A016D2D7F@mailc03.aurigin.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ok,
seems that story came to the end,
corrupted index or table,
after full table reload and index rebuild ( that is by itself very
painful
procedure, especially if number of row ~50M )
works, may be problem resolved.
-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Sunday, June 29, 2003 3:25 PM
To: Maksim Likharev
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] PG crash on simple query
"Maksim Likharev" <mlikharev(at)aurigin(dot)com> writes:
> LOG: server process (pid 2004) was terminated by signal 11
> Is there any way to see what really happened?
I would like to see a stack backtrace (get a core dump, use gdb
on it. See the archives for descriptions of the standard procedure...)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Dann Corbit | 2003-07-02 00:29:45 | Re: Duplicate key insert question |
Previous Message | Dann Corbit | 2003-07-02 00:21:14 | Re: ERROR: language "c" is not trusted |