Re: pg_upgrade & tablespaces

From: Joseph Kregloh <jkregloh(at)sproutloud(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
Cc: John R Pierce <pierce(at)hogranch(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_upgrade & tablespaces
Date: 2013-12-27 21:00:56
Message-ID: CAAW2xff+aqtZoATDMECaKdoXuFJ4b5KSqu+T8=G0xuc6UzEG+w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

>
>
> Postgres is going to /usr/local/pgsql/data/drupal_dbspace/ to look for
> the 9.0 files instead of /usr/local/pgsql_90/data/drupal_dbspace/ and is
> trying to copy them as 9.3 versions into the new default location which has
> the same path. Since the new /usr/local/pgsql/data/drupal_dbspace/PG_9.0_201008051
> is empty it is failing.
>

That is exactly what is going on. I think what I am going to end up doing
is:

- Leaving 9.0 in the default location, this way it will successfully
complete PG upgrade.
- Uninstall 9.0
- Manually move the user created tablespaces into the 9.3 data folder
- Reinstall 9.3 to go into the default location, right now its installed in
/opt using the PREFIX
- Move the 9.3 data folder into the default location.
- Cleanup the old 9.0 folders

Then in theory it should start right up.

I would assume that if the user created tablespaces were created outside of
the /data folder then this would not be an issue. But again, I am not the
DBA, I clean up after everybody else.

Thanks for all your help Adrian.

-Joseph

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2013-12-27 21:15:55 Re: pg_upgrade & tablespaces
Previous Message Adrian Klaver 2013-12-27 20:22:05 Re: pg_upgrade & tablespaces

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2013-12-27 21:02:19 Re: [PATCH] SQL assertions prototype
Previous Message Kevin Grittner 2013-12-27 20:52:43 Re: [BUGFIX] Typos when using the memcmp() function.