Re: [GENERAL] Tape backup, 2 versions, same database name, which is pg_dump backing up

2006-08-02 Thread Thomas F. O'Connell
On Aug 2, 2006, at 4:27 PM, [EMAIL PROTECTED] wrote:You're correct, I cannot use the pg_dump. I get a error message that the pg_dump is aborting because of a version mismatch, then it says to use the i opt. How do I call the pg_dump from the 8.1.4 version?You'll probably need to specify an absolut

Re: [GENERAL] Tape backup, 2 versions, same database name, which is pg_dump backing up

2006-08-02 Thread Thomas F. O'Connell
Your confirmation is correct with one slight technical exception: specifying the port doesn't technically cause the system to know which version of postgres to use.In my previous post, I forgot to mention a related note: the version of pg_dump that you're using matters slightly. pg_dump can typical

Re: [GENERAL] Tape backup, 2 versions, same database name, which is pg_dump backing up

2006-08-02 Thread Thomas F. O'Connell
You'll need to specify the non-default port explicitly in your pg_dump command in order to back up the postmaster running on 55432.E.g., pg_dump -p 55432 -U postgres -C -D -f /tmp/$(date+%F)owl.sql owlBy default, the postgres command-line utilities attempt to connect to 5432 (or $PGPORT or whatever

[GENERAL] Tape backup, 2 versions, same database name, which is pg_dump backing up

2006-08-02 Thread MargaretGillon
Yesterday a consultant upgraded me from 7.3.4 to 8.1.4 on a RedHat 9 server. To make sure everything was okay we left the server so that both versions of Postgresql load. 7.3.4 loads on the default port of 5432 and 8.1.4 loads on port 55432 . My database was moved into the new version so both the