Thank you for the reply.
It has nothing to do with programming. I was trying to back up the 8.1 database (using pg_dump) which had exceeded 2Gig limit according to a response. When I tried to restore it using pg_restore to a 9.0 database, it complained about custom archiver error and corruption and the whole backup stopped.
One response told me to try backing up 8.1 database using 9.0 pg_dump and restore it to 9.0 database using 9.0 pg_restore. Another option, I can think of, is to back up each table one at time and restore it one by one. This way the 2G limit will never come up during the backup. However, it requires a lot of works.
Any suggestion?
Thanks,
2011/4/16 pasman pasmański
<pasman.p@gmail.com>Hi.
It is sometimes hard to tune complicated queries. Maybe add new
attribute to functions returning boolean - selectivity, defining how
big is percent of rows for which the function returns true.
2011/4/15, Edison So <edison.so2@gmail.com>:
> I have a DELL server running Windows server 2003 and Postgres 8.1.
>
> I used pg_dump to back up a database test:
>
> pg_dump -v -h localhost -p 5432 -U postgres -F c -b -f
> "D:/db_dump/backup.bak" test
>
> The backup was showing the following error.
> .
> pg_dump: dumping contents of table history
> pg_dump: [custom archiver] WARNING: ftell mismatch with expected position --
> ftell used
>
> pg_dump: dumping contents of table history_archive
>
> pg_dump: [custom archiver] WARNING: ftell mismatch with expected position --
> ftell used
>
> pg_dump: dumping contents of table historymetadata
>
> pg_dump: [custom archiver] WARNING: ftell mismatch with expected position --
> ftell used
>
> I was trying to do a Posgres 8.1.4 backup and restored it to Postgres 9.0 on
> a new Dell server running Windows server 2008.
>
> Any clue how to resolve it?
>
> Edison
>
> --
> Edison
>
--
------------
pasman
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
--
Edison