Re: BUG #5238: frequent signal 11 segfaults

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Nagy Daniel <nagy(dot)daniel(at)telekom(dot)hu>
Cc: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #5238: frequent signal 11 segfaults
Date: 2009-12-13 03:13:05
Message-ID: 16054.1260673985@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Nagy Daniel <nagy(dot)daniel(at)telekom(dot)hu> writes:
> Here's a better backtrace:

The crash location suggests a problem with a corrupted tuple, but it's
impossible to guess where the tuple came from. In particular I can't
guess whether this reflects on-disk data corruption or some internal
bug. Now that you have (some of) the query, can you put together a test
case? Or try "select * from" each of the tables used in the query to
check for on-disk corruption.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Nagy Daniel 2009-12-13 09:31:54 Re: BUG #5238: frequent signal 11 segfaults
Previous Message Nagy Daniel 2009-12-12 21:26:22 Re: BUG #5238: frequent signal 11 segfaults