>
>
> With Best Regards
> Akshay
> Ericsson OSS MON
> Tata Consultancy Services
> Mailto: akshay.ballarp...@tcs.com
> Website: http://www.tcs.com <http://www.tcs.com/>
> __________
9/2018 06:24 PM
Subject: Re: pg_upgrade help
Hi Fabio,
I think you have found the problem. Please find o/p below.
-bash-4.2$ ps -aef | grep postgres
postgres 478 1 0 13:40 ?00:00:00 /usr/bin/postgres -p 50432
-D /var/ericsson/esm-data/postgresql-data/
postgres 490
-general@lists.postgresql.org
Date: 04/19/2018 03:45 PM
Subject:Re: pg_upgrade help
Hi,
while trying to reproduce your problem, i noticed that on my Centos 6
installations Postgres 8.4 and Postgres 9.6 (I do not have 9.4 readily
available) store the socket in different places:
quot; -o "-p 50432 -c autovacuum=off -c
> autovacuum_freeze_max_age=20 -c listen_addresses='' -c
> unix_socket_permissions=0700" start
> Failure, exiting
>
> With Best Regards
> Akshay
>
g
________
From: Fabio Pardi
To: Akshay Ballarpure
Cc: pgsql-general@lists.postgresql.org
Date: 04/18/2018 06:17 PM
Subject:Re: pg_upgrade help
did you run initdb on the new db?
what happens if you manually start the new db?
/opt/rh/
Hello Akshay,
Try starting both servers individually. If you can then,it may be port
conflict
Below is the part of document-
Obviously, no one should be accessing the clusters during the upgrade.
pg_upgrade defaults to running servers on port 50432 to avoid unintended
client connections. You can
On 04/18/2018 05:02 AM, Akshay Ballarpure wrote:
Hi Fabio,
sorry to bother you again, its still failing with stopping both server
(8.4 and 9.4)
Actually according to the command show at bottom of post it is failing
trying to start the 8.4 server. In your previous post that was because
it was
_________
>
>
>
>
> From: Fabio Pardi
> To: Akshay Ballarpure ,
> pgsql-general@lists.postgresql.org
> Date: 04/18/2018 02:35 PM
> Subject: Re: pg_upgrade help
> --
From: Fabio Pardi
To: Akshay Ballarpure ,
pgsql-general@lists.postgresql.org
Date: 04/18/2018 02:35 PM
Subject:Re: pg_upgrade help
Hi,
i was too fast in reply (and perhaps i should drink my morning coffee
before replying), I will try to be more detailed:
both se
-data/postgresql-data-9.4/postmaster.pid
> 9900
> /var/ericsson/esm-data/postgresql-data-9.4
> 1524039630
> 5432
> /var/run/postgresql
> localhost
> 5432001 2031616
>
>
> [root@ms-esmon /]# cat
> ./var/ericsson/esm-data/postgresql-data/postmaster.pid
> 9778
&
Hi
Both version should be correctly stopped. pg_upgrade started clusters itself.
Please check pg_upgrade_server.log file in directory where pg_upgrade was run.
Also where is postgresql.conf? In PGDATA? Otherwise you need tell pg_upgrade
correct path, for example with options '-o " -c
config_file=
From: Fabio Pardi
To: Akshay Ballarpure ,
pgsql-general@lists.postgresql.org
Date: 04/18/2018 01:06 PM
Subject:Re: pg_upgrade help
Hi,
please avoid crossposting to multiple mailing lists.
You need to run both versions of the database, the old and the new.
They need to r
Hi,
please avoid crossposting to multiple mailing lists.
You need to run both versions of the database, the old and the new.
They need to run on different ports (note that it is impossible to run 2
different processes on the same port, that's not a postgresql thing)
On 04/18/2018 09:30 AM, A
13 matches
Mail list logo
