JRV problem with pg_upgrade

Started by RAVALET Jacquesabout 13 years ago2 messagesbugs
Jump to latest
#1RAVALET Jacques
jacques.ravalet@prestataire.finances.gouv.fr

Hello,

I'am a database administrateur and I get trouble to upgrade database postgres
from 8.4.6 to 9.2.3.

During pg_upgrade, I can't start the old cluster with parameter -c
listen_addresses=''

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=off

-c autovacuum_freeze_max_age=2000000000 -c listen_addresses='*' -c
unix_socket_permissions=0700" start

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=off

-c autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c
unix_socket_permissions=0700" start

But pg_upgrade use this "bad" syntax even I try to force -c
listen_addresses='*'

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='*'"

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=off -c autovacuum_freeze_max_age=2000000000

-c listen_addresses='*' -c listen_addresses='' -c
unix_socket_permissions=0700" start

Failure, exiting

I don't know how to workaround this problem ?

Best regards,

Jacques ravalet

#2Bruce Momjian
bruce@momjian.us
In reply to: RAVALET Jacques (#1)
Re: JRV problem with pg_upgrade

Please run pg_ctl manually on the failed cluster and get the error
message reported, or find out how to make it work successfully.

---------------------------------------------------------------------------

On Mon, Mar 25, 2013 at 04:19:48PM +0100, RAVALET Jacques wrote:

Hello,

I'am a database administrateur and I get trouble to upgrade database postgres
from 8.4.6 to 9.2.3.

During pg_upgrade, I can't start the old cluster with parameter -c
listen_addresses=''

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=off

-c autovacuum_freeze_max_age=2000000000 -c listen_addresses='*' -c
unix_socket_permissions=0700" start

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=off

-c autovacuum_freeze_max_age=2000000000 -c listen_addresses='' -c
unix_socket_permissions=0700" start

But pg_upgrade use this "bad" syntax even I try to force -c listen_addresses=
'*'

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='*'"

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=off -c autovacuum_freeze_max_age=2000000000

-c listen_addresses='*' -c listen_addresses='' -c unix_socket_permissions=0700"
start

Failure, exiting

I don't know how to workaround this problem ?

Best regards,

Jacques ravalet

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs