Re: pg_upgrade error - Mailing list pgsql-admin

Hi Bruce, 

On another cluster, I fixed the old cluster tablespace location by running bellow statement.

update pg_tablespace set spclocation='/opt/symcor-foa/data/pg_tblspc/federator' where spcname='federator';
select * from pg_tablespace 

, but it still fails with same error. There is no symlink in this cluster. 

/opt/symcor-foa/data/pg_tblspc/federator/PG_9.0_201008051/17055/11838
linking "/opt/symcor-foa/data/pg_tblspc/federator/PG_9.0_201008051/17055/11838" to
"/opt/symcor-foa/data/pg_tblspc/federator/PG_9.4_201409291/16423/13013"
error while creating link for relation "pg_catalog.pg_largeobject"
("/opt/symcor-foa/data/pg_tblspc/federator/PG_9.0_201008051/17055/11838"to
"/opt/symcor-foa/data/pg_tblspc/federator/PG_9.4_201409291/16423/13013"):No such file or directory
 

Thanks,
Yogi


-----Original Message-----
From: Bruce Momjian [mailto:bruce@momjian.us] 
Sent: Monday, December 07, 2015 4:05 PM
To: Yogi Barot
Cc: 'pgsql-admin@postgresql.org'
Subject: Re: [ADMIN] pg_upgrade error

On Mon, Dec  7, 2015 at 05:44:06PM +0000, Yogi Barot wrote:
> Hi,
> 
>  
> 
> I am doing pg upgrade from postgresql 9.0.19 to postgresql 9.4 CE version.
> 
>  
> 
> Database size is 300GB.
> 
> Pg_upgade check runs fine but pg_upgrade fails with following error:
> 
>  
> 
> linking 
> "/opt/symcor-foa/pgsql/data/pg_tblspc/federator/PG_9.0_201008051/
> 10349572/11838" to "/opt/symcor-foa/pgsql/data/pg_tblspc/federator/
> PG_9.4_201409291/16434/13013"
> 
>  
> 
> error while creating link for relation "pg_catalog.pg_largeobject" 
> ("/opt/ symcor-foa/pgsql/data/pg_tblspc/federator/PG_9.0_201008051/10349572/11838" to "
> /opt/symcor-foa/pgsql/data/pg_tblspc/federator/PG_9.4_201409291/16434/13013"):
> No such file or directory
> 
> Failure, exiting
> 
>  
> 
> How can I resolve this or resume upgrade?
> 
> The directory 
> "/opt/symcor-foa/pgsql/data/pg_tblspc/federator/PG_9.0_201008051/
> 10349572/11838” does not exist in old cluster, how can I change or 
> remove reference to this directory?

My guess is that you have a mismatch between the symbolic links used in data/pg_tblspc/ and pg_tablespace.spclocation.

pg_tablespace.spclocation. was removed in Postgres 9.2, but in older releases you could have moved the tablespace
withoutupdating that field, causing pg_upgrade failures.
 

-- 
  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
confidentialinformation. 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.