X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 71938D1B26D for ; Tue, 8 Jun 2004 15:11:01 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 95719-08 for ; Tue, 8 Jun 2004 18:10:59 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id E7D17D1B16A for ; Tue, 8 Jun 2004 15:10:57 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i58IAwWY004625; Tue, 8 Jun 2004 14:10:58 -0400 (EDT) To: "Chris Hoover" Cc: pgsql-admin@postgresql.org Subject: Re: Help requeted with abend. In-reply-to: <40C5EE86.8050509@sermonaudio.com> References: <40C5EE86.8050509@sermonaudio.com> Comments: In-reply-to "Chris Hoover" message dated "Tue, 08 Jun 2004 12:51:18 -0400" Date: Tue, 08 Jun 2004 14:10:58 -0400 Message-ID: <4624.1086718258@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200406/92 X-Sequence-Number: 13752 "Chris Hoover" writes: > I just tried to pg_dump a db of mine and recieved the following abend. > Can someone please give me some guidance as to what is going on? I just > created the db yesturday as part of a db migration plan. > pg_dump: ERROR: MemoryContextAlloc: invalid request size 4294967293 This looks like a corrupted-data problem, specifically a variable-length field whose length word contains a ridiculous value. Probably the first thing to do is determine exactly where the bad data is. You can eliminate columns if you can select them successfully, and then home in on the row location by seeing where a "SELECT LIMIT n" fails. People also sometimes use pg_filedump to look at clobbered data --- if you search the archives for threads mentioning pg_filedump, you'll find more detail about this sort of thing than I feel like going into right now. It would of course be interesting to find out how the data got corrupted, but the first step is to gather evidence... regards, tom lane