Received: from makus.postgresql.org ([98.129.198.125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TDyOl-00084a-Vt for pgsql-admin@postgresql.org; Tue, 18 Sep 2012 14:03:36 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TDyOf-00047L-Gf for pgsql-admin@postgresql.org; Tue, 18 Sep 2012 14:03:35 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id q8IE3SA7014858; Tue, 18 Sep 2012 10:03:28 -0400 (EDT) From: Tom Lane To: "himanshu.joshi" cc: pgsql-admin@postgresql.org Subject: Re: Problem in taking the database dump In-reply-to: <50583784.9000100@orkash.com> References: <50583784.9000100@orkash.com> Comments: In-reply-to "himanshu.joshi" message dated "Tue, 18 Sep 2012 14:27:40 +0530" Date: Tue, 18 Sep 2012 10:03:28 -0400 Message-ID: <14857.1347977008@sss.pgh.pa.us> X-Pg-Spam-Score: -2.4 (--) X-Archive-Number: 201209/102 X-Sequence-Number: 40043 "himanshu.joshi" writes: > I am facing a strange problem while taking dump of a postgres > database using pg_dump. > whenever I start the pg_dump command to take the backup of that > particular database, it stops within few minutes with the below > mentioned error: > *[root@s8-msd-2 bin]# ./pg_dump -Upostgres pdc_uima_dummy > > /hdd2-1/pdc_uima_dummy_108_18092012.sql > pg_dump: SQL command failed > pg_dump: Error message from server: ERROR: invalid memory alloc request > size 18446744073709551613 > pg_dump: The command was: COPY public.object_data (id, wkb_geometry, > obj_type_id, obj_beginoffset, obj_endoffset, source_id, sentence_id, > last_mod_date, obj_norm_value, obj_text, entity_name, frequency) TO > stdout;* This looks like a data corruption issue -- that is, there's some row in that table that contains a damaged variable-width field, such that the system is computing a silly value for the width of the field. You need to find and remove the damaged row(s). regards, tom lane