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
This is for your reference and information.
Thanks and regards,
Satheesan K Nair
----- Original Message -----
From: "Magnus Hagander" <magnus(at)hagander(dot)net>
To: "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: "Satheesan K Nair" <support(at)shakthiinnovators(dot)com>;
Sent: Monday, October 31, 2011 4:57 PM
Subject: Re: [BUGS] pg_restore: [custom archiver] error during file seek:
On Mon, Oct 31, 2011 at 12:03, Heikki Linnakangas
> 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
> 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
> EOL by the end of December
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
>> 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
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.
In response to
pgsql-bugs by date
|Next:||From: Naoya Anzai||Date: 2011-11-02 04:44:23|
|Subject: BUG #6283: About the behavior of indexscan in case there are some NULL values.|
|Previous:||From: Finlay Thompson||Date: 2011-11-02 03:54:53|
|Subject: Re: BUG #6275: Horrible performance regression|