Thread: pg_restore: [custom archiver] error during file seek: Invalid argument
pg_restore: [custom archiver] error during file seek: Invalid argument
From
"Satheesan K Nair"
Date:
Dear Supporter, We are trying to restore a 3.2GB sized POstgreSql 8.1 Data base. When it is= reaching a particular table restoration, giving error as "pg_restore: [cus= tom archiver] error during file seek: Invalid argument" and exiting the res= toration. Then when we have googled it, we found that PostgreSql will not support a B= ackup file of more than 2 GB. We would like to know that any of later Versi= ons of the PostgreSql have been got fixed this problem? Awaiting for your reply. Satheesan K Nair India=
Re: pg_restore: [custom archiver] error during file seek: Invalid argument
From
Heikki Linnakangas
Date:
On 31.10.2011 07:55, Satheesan K Nair wrote: > We are trying to restore a 3.2GB sized POstgreSql 8.1 Data base. When it is reaching a particular table restoration, givingerror as "pg_restore: [custom archiver] error during file seek: Invalid argument" and exiting the restoration. > > Then when we have googled it, we found that PostgreSql will not support a Backup file of more than 2 GB. We would liketo know that any of later Versions of the PostgreSql have been got fixed this problem? I belive PostgreSQL has been able to handle that since version 7.3, if the operating system support is there. What operating system and version do you use? -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com
Re: pg_restore: [custom archiver] error during file seek: Invalid argument
From
Heikki Linnakangas
Date:
On 31.10.2011 12:12, Satheesan K Nair wrote: > Our Operating System is Windows XP. > > Should we need to do any changes in any kind of configurations in > Windows XP or PostgreSql?? According to the commit logs, there was a win32-related fix to this on 8.2, and some further MinGW-related changes in 8.4. Regardless of this issue, I'd suggest that you upgrade to the latest version, 9.1.1. 8.1 isn't supported anymore, and 8.2 is just about to reach EOL by the end of December (http://wiki.postgresql.org/wiki/PostgreSQL_Release_Support_Policy). > We are trying to restore the data base backup in 8.1 version through 9.1 > PGAdmin III. > > PGDump ran through "Fedora Linux 10 (Data Base Server) OS". > > Is there any other chance to give the above error? I meant something like, > 1.pgdump not completed the dumping properly, > 2.the Backup file is not saved/copied properly, etc?? I believe the dump is OK, but restoring it doesn't work on version 8.1 on Windows. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com
Re: pg_restore: [custom archiver] error during file seek: Invalid argument
From
Magnus Hagander
Date:
On Mon, Oct 31, 2011 at 12:03, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote: > On 31.10.2011 12:12, Satheesan K Nair wrote: >> >> Our Operating System is Windows XP. >> >> Should we need to do any changes in any kind of configurations in >> Windows XP or PostgreSql?? > > According to the commit logs, there was a win32-related fix to this on 8.= 2, > and some further MinGW-related changes in 8.4. > > Regardless of this issue, I'd suggest that you upgrade to the latest > version, 9.1.1. 8.1 isn't supported anymore, and 8.2 is just about to rea= ch > EOL by the end of December > (http://wiki.postgresql.org/wiki/PostgreSQL_Release_Support_Policy). Note that 8.1 was EOL'ed on Windows specifically even earlier than it was in general. >> We are trying to restore the data base backup in 8.1 version through 9.1 >> PGAdmin III. >> >> PGDump ran through "Fedora Linux 10 (Data Base Server) OS". >> >> Is there any other chance to give the above error? I meant something lik= e, >> 1.pgdump not completed the dumping properly, >> 2.the Backup file is not saved/copied properly, etc?? > > I believe the dump is OK, but restoring it doesn't work on version 8.1 on > Windows. A workaround could be to run pg_restore on a 64-bit Unix box, talking to postgresql server on Windows. That should work around the issue - since the bug is in pg_dump/pg_restore and not in the backend. But I second and thid Heikkis recommendation that you need to get off version 8.1 and onto something more recent as quickly as possible. --=20 =A0Magnus Hagander =A0Me: http://www.hagander.net/ =A0Work: http://www.redpill-linpro.com/
Re: pg_restore: [custom archiver] error during file seek: Invalid argument
From
"Satheesan K Nair"
Date:
ok... let me try the same and check..... Thanks for your valuable support. ----- Original Message ----- From: "Heikki Linnakangas" <heikki.linnakangas@enterprisedb.com> To: "Satheesan K Nair" <support@shakthiinnovators.com> Cc: <pgsql-bugs@postgresql.org> Sent: Monday, October 31, 2011 4:33 PM Subject: Re: [BUGS] pg_restore: [custom archiver] error during file seek: Invalid argument > On 31.10.2011 12:12, Satheesan K Nair wrote: >> Our Operating System is Windows XP. >> >> Should we need to do any changes in any kind of configurations in >> Windows XP or PostgreSql?? > > According to the commit logs, there was a win32-related fix to this on > 8.2, and some further MinGW-related changes in 8.4. > > Regardless of this issue, I'd suggest that you upgrade to the latest > version, 9.1.1. 8.1 isn't supported anymore, and 8.2 is just about to > reach EOL by the end of December > (http://wiki.postgresql.org/wiki/PostgreSQL_Release_Support_Policy). > >> We are trying to restore the data base backup in 8.1 version through 9.1 >> PGAdmin III. >> >> PGDump ran through "Fedora Linux 10 (Data Base Server) OS". >> >> Is there any other chance to give the above error? I meant something >> like, >> 1.pgdump not completed the dumping properly, >> 2.the Backup file is not saved/copied properly, etc?? > > I believe the dump is OK, but restoring it doesn't work on version 8.1 on > Windows. > > -- > Heikki Linnakangas > EnterpriseDB http://www.enterprisedb.com
Re: pg_restore: [custom archiver] error during file seek: Invalid argument
From
"Satheesan K Nair"
Date:
Hi Heiki, Our Operating System is Windows XP. Should we need to do any changes in any kind of configurations in Windows XP or PostgreSql?? We are trying to restore the data base backup in 8.1 version through 9.1 PGAdmin III. PGDump ran through "Fedora Linux 10 (Data Base Server) OS". Is there any other chance to give the above error? I meant something like, 1.pgdump not completed the dumping properly, 2.the Backup file is not saved/copied properly, etc?? Satheesan K Nair India ----- Original Message ----- From: "Heikki Linnakangas" <heikki.linnakangas@enterprisedb.com> To: "Satheesan K Nair" <support@shakthiinnovators.com> Cc: <pgsql-bugs@postgresql.org> Sent: Monday, October 31, 2011 3:25 PM Subject: Re: [BUGS] pg_restore: [custom archiver] error during file seek: Invalid argument > On 31.10.2011 07:55, Satheesan K Nair wrote: >> We are trying to restore a 3.2GB sized POstgreSql 8.1 Data base. When it >> is reaching a particular table restoration, giving error as "pg_restore: >> [custom archiver] error during file seek: Invalid argument" and exiting >> the restoration. >> >> Then when we have googled it, we found that PostgreSql will not support a >> Backup file of more than 2 GB. We would like to know that any of later >> Versions of the PostgreSql have been got fixed this problem? > > I belive PostgreSQL has been able to handle that since version 7.3, if the > operating system support is there. What operating system and version do > you use? > > -- > Heikki Linnakangas > EnterpriseDB http://www.enterprisedb.com
Re: pg_restore: [custom archiver] error during file seek: Invalid argument
From
"Satheesan K Nair"
Date:
Hi Magnus & Heiki, The above problem solved when I have connected 8.1 server through PgAdmin III OF 9.1 version and restored. So, I think there was some bug fix related to the above problem in PgSql 9.1 pg_restore.exe. This is for your reference and information. Thanks and regards, Satheesan K Nair India ----- Original Message ----- From: "Magnus Hagander" <magnus@hagander.net> To: "Heikki Linnakangas" <heikki.linnakangas@enterprisedb.com> Cc: "Satheesan K Nair" <support@shakthiinnovators.com>; <pgsql-bugs@postgresql.org> Sent: Monday, October 31, 2011 4:57 PM Subject: Re: [BUGS] pg_restore: [custom archiver] error during file seek: Invalid argument On Mon, Oct 31, 2011 at 12:03, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote: > On 31.10.2011 12:12, Satheesan K Nair wrote: >> >> Our Operating System is Windows XP. >> >> Should we need to do any changes in any kind of configurations in >> Windows XP or PostgreSql?? > > According to the commit logs, there was a win32-related fix to this on > 8.2, > and some further MinGW-related changes in 8.4. > > Regardless of this issue, I'd suggest that you upgrade to the latest > version, 9.1.1. 8.1 isn't supported anymore, and 8.2 is just about to > reach > EOL by the end of December > (http://wiki.postgresql.org/wiki/PostgreSQL_Release_Support_Policy). Note that 8.1 was EOL'ed on Windows specifically even earlier than it was in general. >> We are trying to restore the data base backup in 8.1 version through 9.1 >> PGAdmin III. >> >> PGDump ran through "Fedora Linux 10 (Data Base Server) OS". >> >> Is there any other chance to give the above error? I meant something >> like, >> 1.pgdump not completed the dumping properly, >> 2.the Backup file is not saved/copied properly, etc?? > > I believe the dump is OK, but restoring it doesn't work on version 8.1 on > Windows. A workaround could be to run pg_restore on a 64-bit Unix box, talking to postgresql server on Windows. That should work around the issue - since the bug is in pg_dump/pg_restore and not in the backend. But I second and thid Heikkis recommendation that you need to get off version 8.1 and onto something more recent as quickly as possible. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/