On 12/26/2013 01:06 PM, Joseph Kregloh wrote:
Here is the message on --hackers that explains the above:
http://www.postgresql.org/__message-id/20130214052952.__GA10606@xxxxxxxxxx
<http://www.postgresql.org/message-id/20130214052952.GA10606@xxxxxxxxxx>
Let me read into this.
No it does not because pg_upgrade doesn't seem to be able to handle
tablespaces, which is the problem I have been having all along and I
keep on proving it. Below is the error when moving the 9.0 directory
with a tablespace:
So how are you moving the 9.0 directory?
What does a listing for that directory look like after the move?
What does a listing for the 9.3 directory look like?
[pgsql@postgres-93-upgrade /tmp]$ time /opt/bin/pg_upgrade -d
/usr/local/pgsql_90/data -D /usr/local/pgsql/data/ -b /usr/local/bin/ -B
/opt/bin/ -p 5452 -P 5451
ok
Removing support functions from new cluster ok
Copying user relation files
.../pgsql/data/drupal_dbspace/PG_9.0_201008051/24659/11790
error while copying relation "pg_catalog.pg_largeobject"
("/usr/local/pgsql/data/drupal_dbspace/PG_9.0_201008051/24659/11790" to
"/usr/local/pgsql/data/drupal_dbspace/PG_9.3_201306121/16421/12301"): No
such file or directory
So what do the listings for the old and new data directories look like
after the upgrade?
Failure, exiting
--
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
