Never mind... It was a version problem, but there is a workaround.
Sincerely,
r.
-----Original Message-----
From: pgsql-novice-owner@postgresql.org
[mailto:pgsql-novice-owner@postgresql.org] On Behalf Of Reshat Sabiq
Sent: Wednesday, December 25, 2002 4:06 AM
To: 'PGSQL Novice List'
Subject: Re: [NOVICE] Moving a database-sos
Actually, 1.7 is the dump version which means that the destination
server does not understand the dump version on the source (which is
understood for restoring on the source as I checked). Apparently, that
is because source is 7.3.1, whereas destination is 7.2.3.
I am still planning to try smt. else, maybe a different way around the
destination's restoration will get the idea.
Sincerely,
r.
-----Original Message-----
From: pgsql-novice-owner@postgresql.org
[mailto:pgsql-novice-owner@postgresql.org] On Behalf Of Reshat Sabiq
Sent: Wednesday, December 25, 2002 3:58 AM
To: 'PGSQL Novice List'
Subject: Re: [NOVICE] Moving a database-sos
After putting it into an archive with pg_dump, I got:
pg_restore: [archiver] unsupported version (1.7) in file header
on destination machine. It's not clear what 1.7 is though, cause all
pg... version involved are 7.x.y, whereas tar versions are both 1.13.25.
P.S. Going to try 2 more things on my mind.
Sincerely,
r.
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
