Re: pg_upgrade 10.2

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Murthy Nunna <mnunna(at)fnal(dot)gov>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org>, "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_upgrade 10.2
Date: 2018-06-12 21:34:52
Message-ID: 4b66fd13-951c-fab6-a618-d27860ba465b@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-general pgsql-performance

On 06/12/2018 02:18 PM, Murthy Nunna wrote:
> pg_upgrade -V
> pg_upgrade (PostgreSQL) 10.4
>
> pg_upgrade -b /fnal/ups/prd/postgres/v9_3_14_x64/Linux-2-6/bin -B /fnal/ups/prd/postgres/v10_4_x64/Linux-2-6/bin -d /data0/pgdata/ifb_prd_last -D /data0/pgdata/ifb_prd_last_104 -p 5433 -P 5434 -r -v –c
>
>

Looks good to me. The only thing that stands out is that in your
original post you had:

-p 5432

and above you have:

-p 5433

Not sure if that makes a difference.

The only suggestion I have at the moment is to move -c from the end of
the line to somewhere earlier on the chance that there is a bug that is
not finding it when it's at the end.

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Murthy Nunna 2018-06-12 21:49:32 RE: pg_upgrade 10.2
Previous Message Rui DeSousa 2018-06-12 21:25:40 Re: PostgreSQL 'Corruption & Fragmentation' detection and resolution/fix

Browse pgsql-general by date

  From Date Subject
Next Message Christophe combet 2018-06-12 21:43:17 Re: Out of memory error with PG10.3, 10.4 but not 9.3.19
Previous Message Murthy Nunna 2018-06-12 21:18:07 RE: pg_upgrade 10.2

Browse pgsql-performance by date

  From Date Subject
Next Message Murthy Nunna 2018-06-12 21:49:32 RE: pg_upgrade 10.2
Previous Message Murthy Nunna 2018-06-12 21:18:07 RE: pg_upgrade 10.2