Re: pg_upgrade does not translate tablespace location to new cluster - Mailing list pgsql-general

From Olivier LEVESQUE
Subject Re: pg_upgrade does not translate tablespace location to new cluster
Date
Msg-id BANLkTimnxsidj4o2gdAm-1bnaWFcKbNZHQ@mail.gmail.com
Whole thread Raw
In response to Re: pg_upgrade does not translate tablespace location to new cluster  (Guillaume Lelarge <guillaume@lelarge.info>)
Responses Re: pg_upgrade does not translate tablespace location to new cluster
List pgsql-general
Guillaume,

Thank you for your answer,


>> Creating databases in the new cluster
>> psql:/opt/pgsql/bin/pg_upgrade_dump_globals.sql:38: ERROR:  directory
>> "/pgqdata/pgserver01/data/tbs_ptest/PG_9.0_201008051" already in use
>> as a tablespace
>>
>
> That would mean that you have a 9.0 tablespace in
> the /pgqdata/pgserver01/data/tbs_ptest directory. Is it true? and IIUC
> your directory layout, it shouldn't.
>

Yes, you're right.  This directory was here from my last succesfull pg_upgrade.

But the problem is that now, data of the new cluster is scattered
across two paths which is not what I expected.


> The only way is to change the code. It shouldn't be too hard, but is
> potentially dangerous.

Why dangerous ? It could be an option.


Regards,
--
Olivier LEVESQUE

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: statically compiling postgres and problem with initdb
Next
From: Guillaume Lelarge
Date:
Subject: Re: pg_upgrade does not translate tablespace location to new cluster