JRV problem with pg_upgrade
От | RAVALET Jacques |
---|---|
Тема | JRV problem with pg_upgrade |
Дата | |
Msg-id | 33DD7B734A847440AD07BD647035F58B03E878C0@DUBLIN.solano.alize обсуждение исходный текст |
Ответы |
Re: JRV problem with pg_upgrade
|
Список | pgsql-bugs |
=20 Hello, I'am a database administrateur and I get trouble to upgrade database = postgres from 8.4.6 to 9.2.3. =20 During pg_upgrade, I can't start the old cluster with parameter -c listen_addresses=3D'' =20 This syntax work to start the old cluster and to access to the database "/distrib/postgresql/app/chfdba/produit/8.4.6/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D = "/distrib/postgresql/data/chorus_formulaires/data" -o "-p 50432 -c autovacuum=3Doff=20 -c autovacuum_freeze_max_age=3D2000000000 -c listen_addresses=3D'*' -c unix_socket_permissions=3D0700" start =20 This syntax doesn't work to start the old cluster "/distrib/postgresql/app/chfdba/produit/8.4.6/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D = "/distrib/postgresql/data/chorus_formulaires/data" -o "-p 50432 -c autovacuum=3Doff=20 -c autovacuum_freeze_max_age=3D2000000000 -c listen_addresses=3D'' -c unix_socket_permissions=3D0700" start =20 But pg_upgrade use this "bad" syntax even I try to force -c listen_addresses=3D'*' =20 pg_upgrade -c -d /distrib/postgresql/data/chorus_formulaires/data -D /distrib/postgresql/data/chorus_formulaires/data/9.2.3 -b /distrib/postgresql/app/chfdba/produit/8.4.6/bin -B /distrib/postgresql/app/chfdba/produit/9.2.3/bin -o "-c = listen_addresses=3D'*'" =20 more pg_upgrade_server.log could not connect to old postmaster started with the command: "/distrib/postgresql/app/chfdba/produit/8.4.6/bin/pg_ctl" -w -l "pg_upgrade_server.log" -D = "/distrib/postgresql/data/chorus_formulaires/data" -o "-p 50432 -c autovacuum=3Doff -c = autovacuum_freeze_max_age=3D2000000000=20 -c listen_addresses=3D'*' -c listen_addresses=3D'' -c unix_socket_permissions=3D0700" start Failure, exiting =20 I don't know how to workaround this problem ? =20 Best regards, =20 Jacques ravalet
В списке pgsql-bugs по дате отправления: