From: Yogi Barot <YBarot@symcor.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: Albe Laurenz <laurenz.albe@wien.gv.at>
Cc: 'pgsql-admin@postgresql.org' <pgsql-admin@postgresql.org>
Subject: Re: Postgresql 9.4 pg_upgrade issues
Date: Tue, 24 Nov 2015 21:45:16 +0000
Message-ID: <2589bd2f0d7e44a1902d20e388351bff@MX002.symprod.com> (raw)
In-Reply-To: <20151124214114.GB24342@momjian.us>
References: <6fb1f76dc5aa4d0a9285aa25ac099476@MX002.symprod.com>
<A737B7A37273E048B164557ADEF4A58B50FEA5DF@ntex2010i.host.magwien.gv.at>
<622de7fb272e489292d5e6b41ae44c29@MX002.symprod.com>
<20151124214114.GB24342@momjian.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Thanks a lot for quick reply.
In this case, If I move table space out of old data directory using symlink, then can I remove old data directory?
-----Original Message-----
From: Bruce Momjian [mailto:bruce@momjian.us]
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,
>
> I was able to manage upgrade testing with cluster which does not have plsh for now.
>
> 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.
>
> Upgrade Complete
> ----------------
> Optimizer statistics are not transferred by pg_upgrade so, once you
> start the new server, consider running:
> analyze_new_cluster.sh
>
> Could not create a script to delete the old cluster's data files
> because user-defined tablespaces exist in the old cluster directory.
> The old cluster's contents must be deleted manually.
>
> 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_ cluster tablespaces.
> 2) Deleting old data directory will effect any functionality of postgresql 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.
--
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 +
CONFIDENTIALITY WARNING
This communication, including any attachments, is for the exclusive use of addressee and may contain proprietary and/or confidential information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies.
AVERTISSEMENT RELATIF À LA CONFIDENTIALITÉ
Ce message, ainsi que les pièces qui y sont jointes, est destiné à l’usage exclusif de la personne à laquelle il s’adresse et peut contenir de l’information personnelle ou confidentielle. Si le lecteur de ce message n’en est pas le destinataire, nous l’avisons par la présente que toute diffusion, distribution, reproduction ou utilisation de son contenu est strictement interdite. Veuillez avertir sur-le-champ l’expéditeur par retour de courrier électronique et supprimez ce message ainsi que toutes les pièces jointes.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: YBarot@symcor.com, bruce@momjian.us, laurenz.albe@wien.gv.at
Subject: Re: Postgresql 9.4 pg_upgrade issues
In-Reply-To: <2589bd2f0d7e44a1902d20e388351bff@MX002.symprod.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox