Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id C0F4F475E22 for ; Tue, 1 Oct 2002 13:10:57 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 18BEC475CB4 for ; Tue, 1 Oct 2002 13:10:57 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.5/8.12.5) with ESMTP id g91HAuhR005836; Tue, 1 Oct 2002 13:10:56 -0400 (EDT) To: Ferdinand Smit Cc: pgsql-admin@postgresql.org Subject: Re: pg_dump error In-reply-to: <200210011752.49941.ferdinand@telegraafnet.nl> References: <200210011752.49941.ferdinand@telegraafnet.nl> Comments: In-reply-to Ferdinand Smit message dated "Tue, 01 Oct 2002 17:52:49 +0200" Date: Tue, 01 Oct 2002 13:10:55 -0400 Message-ID: <5835.1033492255@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200210/7 X-Sequence-Number: 5865 Ferdinand Smit writes: > What does this mean ?!? Is this a corrupt database, a bug or has the pg_dump > not enough memory ? > $ pg_dump login | gzip > login.dump.gz > pg_dump: ERROR: MemoryContextAlloc: invalid request size 4294967293 > pg_dump: lost synchronization with server, resetting connection > pg_dump: SQL command to dump the contents of table "postcodereeks" failed: > PQendcopy() failed. First guess is a corrupted data value in table postcodereeks. Possibly you can narrow down which row(s) have bad data and remove 'em. regards, tom lane