On Thu, Dec 19, 2013 at 12:49 PM, Joseph Kregloh <jkregloh@xxxxxxxxxxxxxx> wrote: > On Thu, Dec 19, 2013 at 3:46 PM, Sergey Konoplev <gray.ru@xxxxxxxxx> wrote: >> On Thu, Dec 19, 2013 at 12:27 PM, Joseph Kregloh >> <jkregloh@xxxxxxxxxxxxxx> wrote: >> > So what I get from this is that it does create the correct 9.3 files in >> > the >> > new location, however it cannot copy the relation over because the old >> > data >> > is in the /home/jkregloh/pg_data/data/drupal_dbspace/ not in >> > /usr/local/pgsql/data/drupal_dbspace/ as the pg_upgrade query tries to >> > do. >> >> Can you show what ls -l /home/jkregloh/pg_data/data/pg_tblspc/ prints, >> please? >> > [pgsql@postgres-93-upgrade ~]$ ls -l /home/jkregloh/pg_data/data/pg_tblspc/ > lrwxr-xr-x 1 pgsql pgsql 41 Dec 19 19:53 11047389 -> > /home/jkregloh/pg_data/data/stats_dbspace > lrwxr-xr-x 1 pgsql pgsql 44 Dec 19 19:53 11047390 -> > /home/jkregloh/pg_data/data/stats_indexspace > lrwxr-xr-x 1 pgsql pgsql 49 Dec 19 19:53 11047391 -> > /home/jkregloh/pg_data/data/stats_staging_dbspace Bruce, may be it's a silly question, but the above makes me think so. I always keep tablespaces in locations different from the main data dir, and never faced something like this. Doesn't pg_upgrade do a stright replace of -d dir with -D dir everywhere in paths? ps. Joseph, please, don't use top-posting, see http://en.wikipedia.org/wiki/Posting_style#Interleaved_style. -- Kind regards, Sergey Konoplev PostgreSQL Consultant and DBA http://www.linkedin.com/in/grayhemp +1 (415) 867-9984, +7 (901) 903-0499, +7 (988) 888-1979 gray.ru@xxxxxxxxx -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
