From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | Edison So <edison(dot)so2(at)gmail(dot)com>, pasman pasmański <pasman(dot)p(at)gmail(dot)com> |
Subject: | Re: New feature: selectivity - new attribute in function |
Date: | 2011-04-16 20:50:33 |
Message-ID: | 201104161350.33694.adrian.klaver@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Saturday, April 16, 2011 1:10:39 pm Edison So wrote:
> 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.
If you are trying to restore forward to 9.0 you will need to use the 9.0 version
of pg_dump in either case. If you are trying to create a backup to use on the
8.1 database you might try -Fp instead of -Fc to create the dump(untested). The
bug seems to be with the binary dump version not the text version.
>
> Any suggestion?
>
> Thanks,
>
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2011-04-16 20:52:30 | Re: New feature: selectivity - new attribute in function |
Previous Message | Edison So | 2011-04-16 20:48:58 | Re: New feature: selectivity - new attribute in function |