Skip site navigation (1) Skip section navigation (2)

Re: Problem in taking the database dump

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "himanshu(dot)joshi" <himanshu(dot)joshi(at)orkash(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Problem in taking the database dump
Date: 2012-09-18 14:03:28
Message-ID: 14857.1347977008@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-admin
"himanshu.joshi" <himanshu(dot)joshi(at)orkash(dot)com> 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(at)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


In response to

pgsql-admin by date

Next:From: Bruce MomjianDate: 2012-09-18 23:22:39
Subject: Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed
Previous:From: C├ędric VillemainDate: 2012-09-18 11:12:56
Subject: Re: Schema diagramming tool?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group