X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 999259FB25E; Fri, 28 Jul 2006 13:32:23 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 61526-06; Fri, 28 Jul 2006 13:32:15 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 602A89FB1F2; Fri, 28 Jul 2006 13:31:45 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k6SGViqp025232; Fri, 28 Jul 2006 12:31:44 -0400 (EDT) To: "Daniel Caune" cc: pgsql-admin@postgresql.org, pgsql-sql@postgresql.org Subject: Re: [SQL] PostgreSQL server terminated by signal 11 In-reply-to: <1E293D3FF63A3740B10AD5AAD88535D202B65395@UBIMAIL1.ubisoft.org> References: <1E293D3FF63A3740B10AD5AAD88535D202B65395@UBIMAIL1.ubisoft.org> Comments: In-reply-to "Daniel Caune" message dated "Fri, 28 Jul 2006 12:09:48 -0400" Date: Fri, 28 Jul 2006 12:31:44 -0400 Message-ID: <25231.1154104304@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.057 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200607/259 X-Sequence-Number: 22505 "Daniel Caune" writes: > The statement "copy gslog_event to stdout;" leads to "ERROR: invalid memory alloc request size 4294967293" after awhile. > ... > I did other tests on some other tables that contain less data but that seem also corrupted: This is a bit scary as it suggests a systemic problem. You should definitely try to find out exactly what the corruption looks like. It's usually not hard to home in on where the first corrupted row is --- you do SELECT ctid, * FROM tab LIMIT n; and determine the largest value of n that won't trigger a failure. The corrupted region is then just after the last ctid you see. You can look at those blocks with "pg_filedump -i -f" and see if anything pops out. Check the PG archives for previous discussions of dealing with corrupted data. regards, tom lane