Обсуждение: pg_dumpall -> by hand without --binary-upgrade or BUG #5690: pg_upgrade fails

In my attempts I changed all pg_hba.conf (8.4 & 9.0) to trusted, turned off=
 firewall,followed instructions to shut down db(s) and ran cmd.exe as postg=
res:

C:\WINDOWS\system32>pg_upgrade.exe -p 5432 -P 5433 -d "c:/program files/pos=
tgresql/8.4/data" -D "c:/program files/postgresql/9.0/data" -b "c:/program =
files/postgresql/8.4/bin" -B "c:/program files/postgresql/9.0/bin"Performin=
g Consistency Checks-----------------------------Checking old data director=
y (c:/program files/postgresql/8.4/data)okChecking old bin directory (c:/pr=
ogram files/postgresql/8.4/bin)okChecking new data directory (c:/program fi=
les/postgresql/9.0/data)okChecking new bin directory (c:/program files/post=
gresql/9.0/bin)okChecking for reg* system oid user data types              =
  okChecking for /contrib/isn with bigint-passing mismatch      okChecking =
for large objects                                  okCreating catalog dump =
                                      Access is denied.

There were problems executing ""c:/program files/postgresql/9.0/bin/pg_dump=
all"--port 5432 --username "postgres" --schema-only --binary-upgrade > "C:\=
WINDOWS\system32/pg_upgrade_dump_all.sql""
I'm not clear if it picked up the 8.4 -p 5432 and 9.0 -P 5433
C:\WINDOWS\system32>pg_dumpall.exe --port 5433 username--"postgres" --schem=
a-only >"c:/windows/system32/pg_upgrade_dump_all.sql"Access is denied.
C:\WINDOWS\system32>pg_dumpall.exe --port 5433 username--"postgres" --passw=
ord "********" --schema-only >"c:/windows/system32/pg_upgrade_dump_all.sql"=
Access is denied.
C:\WINDOWS\system32>pg_dumpall.exe --port 5433 username--"postgres" --passw=
ord ******* --schema-only >"c:/windows/system32/pg_upgrade_dump_all.sql"Acc=
ess is denied.
C:\WINDOWS\system32>pg_dumpall.exe --port 5432 username--"postgres" --passw=
ord ******* --schema-only >"c:/windows/system32/pg_upgrade_dump_all.sql"Acc=
ess is denied.
C:\WINDOWS\system32>pg_dumpall.exe --port 5432 username--"postgres" --passw=
ord ******** --schema-only >"c:/windows/system32/pg_upgrade_dump_all.sql"Ac=
cess is denied.
8.4 Log2010-10-11 18:14:28 EDTLOG:  database system was shut down at 2010-1=
0-11 17:59:17 EDT2010-10-11 18:14:29 EDTLOG:  database system is ready to a=
ccept connections2010-10-11 18:14:35 EDTLOG:  received fast shutdown reques=
t2010-10-11 18:14:35 EDTLOG:  aborting any active transactions2010-10-11 18=
:14:35 EDTLOG:  shutting down2010-10-11 18:14:35 EDTLOG:  database system i=
s shut down
9.0 Log2010-10-11 17:14:18 EDT LOG:  database system was shut down at 2010-=
10-11 16:25:16 EDT2010-10-11 17:14:18 EDT FATAL:  the database system is st=
arting up2010-10-11 17:14:19 EDT LOG:  database system is ready to accept c=
onnections2010-10-11 17:14:19 EDT LOG:  autovacuum launcher started2010-10-=
11 17:34:58 EDT LOG:  received fast shutdown request2010-10-11 17:34:58 EDT=
 LOG:  aborting any active transactions2010-10-11 17:34:58 EDT LOG:  autova=
cuum launcher shutting down2010-10-11 17:34:58 EDT LOG:  shutting down2010-=
10-11 17:34:58 EDT LOG:  database system is shut down
And there we sit, dejected.  Any thoughts would be greatly appreciated.
Chris English



=20=09=09=20=09=20=20=20=09=09=20=20=

On 10/11/10 4:09 PM, Chris English wrote:
>
> C:\WINDOWS\system32>pg_dumpall.exe --port 5433 username--"postgres"
> --schema-onl
> y >"c:/windows/system32/pg_upgrade_dump_all.sql"
> Access is denied.
>

why are you writing the .sql output to the windows system32 directory?!?!?

thats a TERRIBLE place to put that.

On Mon, Oct 11, 2010 at 7:09 PM, Chris English <sglish@hotmail.com> wrote:
> In my attempts=A0I changed all pg_hba.conf (8.4 & 9.0) to trusted, turned=
 off
> firewall,
> followed instructions to shut down db(s) and ran cmd.exe as postgres:
>
> C:\WINDOWS\system32>pg_upgrade.exe -p 5432 -P 5433 -d "c:/program
> files/postgres
> ql/8.4/data" -D "c:/program files/postgresql/9.0/data" -b "c:/program
> files/post
> gresql/8.4/bin" -B "c:/program files/postgresql/9.0/bin"
> Performing Consistency Checks
> -----------------------------
> Checking old data directory (c:/program files/postgresql/8.4/data)ok
> Checking old bin directory (c:/program files/postgresql/8.4/bin)ok
> Checking new data directory (c:/program files/postgresql/9.0/data)ok
> Checking new bin directory (c:/program files/postgresql/9.0/bin)ok
> Checking for reg* system oid user data types =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0ok
> Checking for /contrib/isn with bigint-passing mismatch =A0 =A0 =A0ok
> Checking for large objects =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0ok
> Creating catalog dump =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 =A0 =A0 =A0 Access is
> denied.
>
> There were problems executing ""c:/program
> files/postgresql/9.0/bin/pg_dumpall"
> --port 5432 --username "postgres" --schema-only --binary-upgrade >
> "C:\WINDOWS\s
> ystem32/pg_upgrade_dump_all.sql""
> I'm not clear if it picked up the 8.4 -p 5432 and 9.0 -P 5433
> C:\WINDOWS\system32>pg_dumpall.exe --port 5433 username--"postgres"
> --schema-onl
> y >"c:/windows/system32/pg_upgrade_dump_all.sql"
> Access is denied.
> C:\WINDOWS\system32>pg_dumpall.exe --port 5433 username--"postgres"
> --password "
> ********" --schema-only >"c:/windows/system32/pg_upgrade_dump_all.sql"
> Access is denied.
> C:\WINDOWS\system32>pg_dumpall.exe --port 5433 username--"postgres"
> --password *
> ****** --schema-only >"c:/windows/system32/pg_upgrade_dump_all.sql"
> Access is denied.
> C:\WINDOWS\system32>pg_dumpall.exe --port 5432 username--"postgres"
> --password *
> ****** --schema-only >"c:/windows/system32/pg_upgrade_dump_all.sql"
> Access is denied.
> C:\WINDOWS\system32>pg_dumpall.exe --port 5432 username--"postgres"
> --password *
> ******* --schema-only >"c:/windows/system32/pg_upgrade_dump_all.sql"
> Access is denied.
> 8.4 Log
> 2010-10-11 18:14:28 EDTLOG: =A0database system was shut down at 2010-10-11
> 17:59:17 EDT
> 2010-10-11 18:14:29 EDTLOG: =A0database system is ready to accept connect=
ions
> 2010-10-11 18:14:35 EDTLOG: =A0received fast shutdown request
> 2010-10-11 18:14:35 EDTLOG: =A0aborting any active transactions
> 2010-10-11 18:14:35 EDTLOG: =A0shutting down
> 2010-10-11 18:14:35 EDTLOG: =A0database system is shut down
> 9.0 Log
> 2010-10-11 17:14:18 EDT LOG: =A0database system was shut down at 2010-10-=
11
> 16:25:16 EDT
> 2010-10-11 17:14:18 EDT FATAL: =A0the database system is starting up
> 2010-10-11 17:14:19 EDT LOG: =A0database system is ready to accept connec=
tions
> 2010-10-11 17:14:19 EDT LOG: =A0autovacuum launcher started
> 2010-10-11 17:34:58 EDT LOG: =A0received fast shutdown request
> 2010-10-11 17:34:58 EDT LOG: =A0aborting any active transactions
> 2010-10-11 17:34:58 EDT LOG: =A0autovacuum launcher shutting down
> 2010-10-11 17:34:58 EDT LOG: =A0shutting down
> 2010-10-11 17:34:58 EDT LOG: =A0database system is shut down
> And there we sit, dejected. =A0Any thoughts would be greatly appreciated.
> Chris English

Is there any way we can crank up the debug level during those 20
minutes the new database is up?  Or look at pg_stat_activity?  What is
it doing during all that time?

--=20
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Please try to change you cuttent working directory to a place you have Writ=
e-Access before pg_upgrade

As in cd \temp or cd %Home%


Harald

Am 12.10.2010 um 01:09 schrieb Chris English <sglish@hotmail.com>:

> In my attempts I changed all pg_hba.conf (8.4 & 9.0) to trusted, turned o=
ff firewall,
> followed instructions to shut down db(s) and ran cmd.exe as postgres:
>=20
> C:\WINDOWS\system32>pg_upgrade.exe -p 5432 -P 5433 -d "c:/program files/p=
ostgres
> ql/8.4/data" -D "c:/program files/postgresql/9.0/data" -b "c:/program fil=
es/post
> gresql/8.4/bin" -B "c:/program files/postgresql/9.0/bin"
> Performing Consistency Checks
> -----------------------------
> Checking old data directory (c:/program files/postgresql/8.4/data)ok
> Checking old bin directory (c:/program files/postgresql/8.4/bin)ok
> Checking new data directory (c:/program files/postgresql/9.0/data)ok
> Checking new bin directory (c:/program files/postgresql/9.0/bin)ok
> Checking for reg* system oid user data types                ok
> Checking for /contrib/isn with bigint-passing mismatch      ok
> Checking for large objects                                  ok
> Creating catalog dump                                       Access is den=
ied.
>=20
>=20
> There were problems executing ""c:/program files/postgresql/9.0/bin/pg_du=
mpall"
> --port 5432 --username "postgres" --schema-only --binary-upgrade > "C:\WI=
NDOWS\s
> ystem32/pg_upgrade_dump_all.sql""
>=20
> I'm not clear if it picked up the 8.4 -p 5432 and 9.0 -P 5433
>=20
> C:\WINDOWS\system32>pg_dumpall.exe --port 5433 username--"postgres" --sch=
ema-onl
> y >"c:/windows/system32/pg_upgrade_dump_all.sql"
> Access is denied.
>=20
> C:\WINDOWS\system32>pg_dumpall.exe --port 5433 username--"postgres" --pas=
sword "
> ********" --schema-only >"c:/windows/system32/pg_upgrade_dump_all.sql"
> Access is denied.
>=20
> C:\WINDOWS\system32>pg_dumpall.exe --port 5433 username--"postgres" --pas=
sword *
> ****** --schema-only >"c:/windows/system32/pg_upgrade_dump_all.sql"
> Access is denied.
>=20
> C:\WINDOWS\system32>pg_dumpall.exe --port 5432 username--"postgres" --pas=
sword *
> ****** --schema-only >"c:/windows/system32/pg_upgrade_dump_all.sql"
> Access is denied.
>=20
> C:\WINDOWS\system32>pg_dumpall.exe --port 5432 username--"postgres" --pas=
sword *
> ******* --schema-only >"c:/windows/system32/pg_upgrade_dump_all.sql"
> Access is denied.
>=20
> 8.4 Log
> 2010-10-11 18:14:28 EDTLOG:  database system was shut down at 2010-10-11 =
17:59:17 EDT
> 2010-10-11 18:14:29 EDTLOG:  database system is ready to accept connectio=
ns
> 2010-10-11 18:14:35 EDTLOG:  received fast shutdown request
> 2010-10-11 18:14:35 EDTLOG:  aborting any active transactions
> 2010-10-11 18:14:35 EDTLOG:  shutting down
> 2010-10-11 18:14:35 EDTLOG:  database system is shut down
>=20
> 9.0 Log
> 2010-10-11 17:14:18 EDT LOG:  database system was shut down at 2010-10-11=
 16:25:16 EDT
> 2010-10-11 17:14:18 EDT FATAL:  the database system is starting up
> 2010-10-11 17:14:19 EDT LOG:  database system is ready to accept connecti=
ons
> 2010-10-11 17:14:19 EDT LOG:  autovacuum launcher started
> 2010-10-11 17:34:58 EDT LOG:  received fast shutdown request
> 2010-10-11 17:34:58 EDT LOG:  aborting any active transactions
> 2010-10-11 17:34:58 EDT LOG:  autovacuum launcher shutting down
> 2010-10-11 17:34:58 EDT LOG:  shutting down
> 2010-10-11 17:34:58 EDT LOG:  database system is shut down
>=20
> And there we sit, dejected.  Any thoughts would be greatly appreciated.
>=20
> Chris English
>=20
>=20
>=20
>=20