From: | Jan-Peter(dot)Seifert(at)gmx(dot)de |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: pg_dump etc. versions |
Date: | 2008-09-08 10:05:27 |
Message-ID: | 20080908100527.36590@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hello Peter,
thank you very much for your quick reply again.
> Datum: Thu, 04 Sep 2008 16:43:42 +0300
> Von: Peter Eisentraut <peter_e(at)gmx(dot)net>
> An: Jan-Peter Seifert <Jan-Peter(dot)Seifert(at)gmx(dot)de>
> CC: Postgres <pgsql-admin(at)postgresql(dot)org>
> Betreff: Re: [ADMIN] pg_dump etc. versions
> I think the only thing that we really check is that pg_dump of a newer
> version can dump databases from an older version server. All the other
> tools probably only work (completely) with a server from the same major
> release.
http://www.postgresql.org/docs/8.3/static/release-8-3-3.html
Now I have an idea why I couldn't create and restore a dump with pgAdmin III v1.8.4 with one of our databases. In the older v1.6.3 the same dump could be restored. v1.8.4 came with the 8.3.0.842 version of pg_dump?
I guess the version restriction goes for pgAdmin III as well. If I remember correctly I got an error message on an v8.2 server and one of the possible reasons given by pgAdmin III was an feature that came with v8.3 - can't find the note I took at the moment though.
Thank you very much,
Peter
--
GMX Kostenlose Spiele: Einfach online spielen und Spaß haben mit Pastry Passion!
http://games.entertainment.gmx.net/de/entertainment/games/free/puzzle/6169196
From | Date | Subject | |
---|---|---|---|
Next Message | Sofer, Yuval | 2008-09-08 11:28:48 | problem with pg_stat_activity view |
Previous Message | Peter Eisentraut | 2008-09-08 09:40:50 | Re: server/db encoding (mix) issues |