Re: Testing 9.0beta3 and pg_upgrade - Mailing list pgsql-general

From Thomas Kellerer
Subject Re: Testing 9.0beta3 and pg_upgrade
Date
Msg-id i1hm3r$ol$1@dough.gmane.org
Whole thread Raw
In response to Testing 9.0beta3 and pg_upgrade  (Thomas Kellerer <spam_eater@gmx.net>)
Responses Re: Testing 9.0beta3 and pg_upgrade
List pgsql-general
Thomas Kellerer, 12.07.2010 23:29:
> Hi,
>
> I'm trying pg_upgrade on my Windows installation and I have two
> suggestions for the manual regarding pg_upgrade:
>
> When specifying directories, pg_upgrade *requires* a forward slash as
> the path separator. This is (still) uncommon in the Windows world
> (although Windows does support it) and even though the example in the
> manual does show forward slashes, I think it would be a good idea to
> specifically mention the fact that it will *not* work with a backslash.

There is another misleading error message.

When the old *bin*dir is not specified correctly, pg_upgrade claims the old *data*dir does not exist

Something like:

pg_upgrade --check --old-bindir="c:/Program Files/PostgreSQL/8.4"  ....

(note the missing /bin part)

will cause the following output:

'c:/Program' is not recognized as an internal or external command,
operable program or batch file.
Performing Consistency Checks
-----------------------------
Checking old data directory (c:/Daten/db/pgdata84)
check for postgres failed - No such file or directory

It took me a while to find out that the bindir was wrong, not the datadir. The "c:/Program' is not recognized as an.."
madeit even more confusing. 


Regards
Thomas

pgsql-general by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Writing XML files to Operating System
Next
From: Craig Ringer
Date:
Subject: Atul.Goel@globaldatapoint.com