On 12/27/2013 01:00 PM, Joseph Kregloh wrote:
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.
Got to thinking about this. What you could try is:
Move the 9.3 data directory, with the exception of the tablespace, into
the default location. Leave the upgraded 9.3 tablespace itself in /opt.
- 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
--
Adrian Klaver
adrian.klaver@xxxxxxxxx
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
