Re: Postgresql 9.4 pg_upgrade issues

Поиск
Список
Период
Сортировка
От 'Bruce Momjian'
Тема Re: Postgresql 9.4 pg_upgrade issues
Дата
Msg-id 20151124214608.GC24342@momjian.us
обсуждение исходный текст
Ответ на Re: Postgresql 9.4 pg_upgrade issues  (Yogi Barot <YBarot@symcor.com>)
Список pgsql-admin
On Tue, Nov 24, 2015 at 09:45:16PM +0000, Yogi Barot wrote:
> 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?

Yes.  The warning is there so you don't delete the old cluster's data
directory while it contains tablespaces for the new cluster.  As you can
imagine, that would be a bad thing.

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


>
>
>
> -----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
modewill 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_tblspcsymlinks, 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/orconfidential information. If you are not the intended recipient, any use, copying, disclosure, dissemination or
distributionis strictly prohibited. If you are not the intended recipient, please notify the sender immediately by
returne-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’adresseet 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
contenuest strictement interdite. Veuillez avertir sur-le-champ l’expéditeur par retour de courrier électronique et
supprimezce message ainsi que toutes les pièces jointes. 


--
  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                             +


В списке pgsql-admin по дате отправления:

Предыдущее
От: Yogi Barot
Дата:
Сообщение: Re: Postgresql 9.4 pg_upgrade issues
Следующее
От: "Williams, Alex"
Дата:
Сообщение: Re: Question on Hot Standby in PostgreSQL