Re: Testing 9.0beta3 and pg_upgrade

From: Thomas Kellerer <spam_eater(at)gmx(dot)net>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Testing 9.0beta3 and pg_upgrade
Date: 2010-07-13 12:27:38
Message-ID: i1hm3r$ol$1@dough.gmane.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.." made it even more confusing.

Regards
Thomas

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Craig Ringer 2010-07-13 12:33:42 Atul.Goel@globaldatapoint.com
Previous Message Craig Ringer 2010-07-13 12:26:10 Re: Writing XML files to Operating System