pg_upgrade issues

From: <depstein(at)alliedtesting(dot)com>
To: <pgsql-bugs(at)postgresql(dot)org>
Subject: pg_upgrade issues
Date: 2010-06-18 14:26:05
Message-ID: 29F36C7C98AB09499B1A209D48EAA615B49DD7A5C6@mail2a.alliedtesting.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

PostgreSQL 9.0 beta 2
Windows XP Professional SP2

While migrating the database from 8.4 to 9.0 using pg_upgrade (now part of the Postgres project), the following issues came up:

1. When using the --logfile option, pg_upgrade quits with an error like this:

The process cannot access the file because it is being used by another process.

There were problems executing ""C:\PostgreSQL\8.4\bin/pg_ctl" -l "pg_upgrade.log
" -D "D:\PostgreSQL84_matlab1b" -o "-p 5432 -c autovacuum=off -c autovacuum_free
ze_max_age=2000000000" start >> "pg_upgrade.log" 2>&1"

2. Although pg_upgrade has a username option, this option is not used when pg_dump is called, which tries to use the current logon account name as the user name. As a result, pg_upgrade can only be used when the command shell is launched under the postgres account. (I know that this is mentioned on the doc page, but this doesn't seem right).

3. The old database had the pgadmin debugger installed. The module is part of 8.4 and 9.0 distributions for Windows. However, pg_upgrade reported the following error:

ERROR: could not load library "C:/PostgreSQL/9.0/lib/pldbgapi.dll": The specified module could not be found.

I had to uninstall the debugger from the old database before I could proceed.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message depstein 2010-06-18 15:10:56 Re: pg_upgrade issues
Previous Message Tom Lane 2010-06-18 14:18:21 Re: BUG #5511: Handling of case in Username and database names are inconsistant.

Browse pgsql-hackers by date

  From Date Subject
Next Message depstein 2010-06-18 15:10:56 Re: pg_upgrade issues
Previous Message Tom Lane 2010-06-18 14:21:52 Re: system views for walsender activity