Discussion:
Problem in taking the database dump
(too old to reply)
himanshu.joshi
2012-09-18 08:57:40 UTC
Permalink
Hi,

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:

*[***@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;*

After repeating the process many times I am getting the same error every
time.
Due to space problem in the database server, the tablespace of that
particular database is mounted on another storage server. Is this
mounting is the cause of the error or anything else? Plz suggest.

Thanks & Regards,
Himanshu Joshi
--
Sent via pgsql-admin mailing list (pgsql-***@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Tom Lane
2012-09-18 14:03:28 UTC
Permalink
Post by himanshu.joshi
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
/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
--
Sent via pgsql-admin mailing list (pgsql-***@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Loading...