Received-SPF: None (mr1.symcor.com: no sender authenticity
 information available from domain of YBarot@symcor.com)
 identity=mailfrom; client-ip=172.25.152.12;
 receiver=mr1.symcor.com; envelope-from="YBarot@symcor.com";
 x-sender="YBarot@symcor.com"; x-conformance=spf_only
Received-SPF: None (mr1.symcor.com: no sender authenticity
 information available from domain of
 postmaster@MX002.symprod.com) identity=helo;
 client-ip=172.25.152.12; receiver=mr1.symcor.com;
 envelope-from="YBarot@symcor.com";
 x-sender="postmaster@MX002.symprod.com"; x-conformance=spf_only
Content-Type: multipart/mixed; boundary="===============7737731623827075435=="
MIME-Version: 1.0
From: Yogi Barot <YBarot@symcor.com>
To: 'Bruce Momjian' <bruce@momjian.us>
CC: 'Albe Laurenz' <laurenz.albe@wien.gv.at>, "'pgsql-admin@postgresql.org'"
 <pgsql-admin@postgresql.org>
Subject: Re: Postgresql 9.4 pg_upgrade issues
Thread-Topic: [ADMIN] Postgresql 9.4 pg_upgrade issues
Thread-Index: AdEjAGV3yn9Ef7JGS1GGnVPF7rUGHQD0zrRAAAjLPrAADPzHAAAKa7EQ
Date: Tue, 24 Nov 2015 21:45:16 +0000
Message-ID: <2589bd2f0d7e44a1902d20e388351bff@MX002.symprod.com>
References: <6fb1f76dc5aa4d0a9285aa25ac099476@MX002.symprod.com>
 <A737B7A37273E048B164557ADEF4A58B50FEA5DF@ntex2010i.host.magwien.gv.at>
 <622de7fb272e489292d5e6b41ae44c29@MX002.symprod.com>
 <20151124214114.GB24342@momjian.us>
In-Reply-To: <20151124214114.GB24342@momjian.us>
Accept-Language: en-US
MIME-Version: 1.0
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

--===============7737731623827075435==
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks a lot for quick reply.=20

In this case,  If I move table space out of old data directory using symlin=
k, then can I remove old data directory?


-----Original Message-----
From: Bruce Momjian [mailto:bruce@momjian.us]=20
Sent: Tuesday, November 24, 2015 4:41 PM
To: Yogi Barot
Cc: 'Albe Laurenz'; 'pgsql-admin@postgresql.org'
Subject: Re: [ADMIN] Postgresql 9.4 pg_upgrade issues

On Tue, Nov 24, 2015 at 08:32:18PM +0000, Yogi Barot wrote:
> Hi,
>=20
> I was able to manage upgrade testing with cluster which does not have pls=
h for now.
>=20
> But I have another problem. All my data TB is in the tablespace in PGData=
 directory, I did the upgrade using link method, now I got this warning.=20=
=20
>=20
> Upgrade Complete
> ----------------
> Optimizer statistics are not transferred by pg_upgrade so, once you=20
> start the new server, consider running:
>     analyze_new_cluster.sh
>=20
> Could not create a script to delete the old cluster's data files=20
> because user-defined tablespaces exist in the old cluster directory.=20=20
> The old cluster's contents must be deleted manually.
>=20
> 1) Does This means , I can't delete old cluster data directory? Or I can =
delete it manually?

If you delete the old data directory, you will delete the old _and_ _new_ c=
luster tablespaces.

> 2) Deleting old data directory will effect any functionality of postgresq=
l new cluster?

Yep, you can bet on that.  :-)

> 3) Also Need some clarification on link mode, what if I upgrade from 9.5.=
 to future release using pg_upgarde link mode will still work on same data =
directory?

Yes, but I suggest you shut down your server and move those tablespaces out=
 of the data directory, update the pg_tblspc symlinks, and then restart the=
 server.

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

+ As you are, so once was I. As I am, so you will be. +
+ Roman grave inscription                             +

--===============7737731623827075435==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable


CONFIDENTIALITY WARNING=20
This communication, including any attachments, is for the exclusive use of =
addressee and may contain proprietary and/or confidential information. If y=
ou are not the intended recipient, any use, copying, disclosure, disseminat=
ion or distribution is strictly prohibited. If you are not the intended rec=
ipient, please notify the sender immediately by return e-mail, delete this =
communication and destroy all copies.

AVERTISSEMENT RELATIF =C3=80 LA CONFIDENTIALIT=C3=89=20
Ce message, ainsi que les pi=C3=A8ces qui y sont jointes, est destin=C3=A9 =
=C3=A0 l=E2=80=99usage exclusif de la personne =C3=A0 laquelle il s=E2=80=
=99adresse et peut contenir de l=E2=80=99information personnelle ou confide=
ntielle. Si le lecteur de ce message n=E2=80=99en est pas le destinataire, =
nous l=E2=80=99avisons par la pr=C3=A9sente que toute diffusion, distributi=
on, reproduction ou utilisation de son contenu est strictement interdite. V=
euillez avertir sur-le-champ l=E2=80=99exp=C3=A9diteur par retour de courri=
er =C3=A9lectronique et supprimez ce message ainsi que toutes les pi=C3=A8c=
es jointes.

--===============7737731623827075435==
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0


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

--===============7737731623827075435==--