From: | Olivier LEVESQUE <olevesque3(at)gmail(dot)com> |
---|---|
To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_upgrade does not translate tablespace location to new cluster |
Date: | 2011-07-01 16:30:20 |
Message-ID: | BANLkTimnxsidj4o2gdAm-1bnaWFcKbNZHQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2011-07-01 16:42:49 | Re: pg_upgrade does not translate tablespace location to new cluster |
Previous Message | Tom Lane | 2011-07-01 15:48:39 | Re: statically compiling postgres and problem with initdb |