From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> |
Cc: | Joseph Kregloh <jkregloh(at)sproutloud(dot)com>, Ziggy Skalski <zskalski(at)afilias(dot)info>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_upgrade & tablespaces |
Date: | 2013-12-19 21:18:07 |
Message-ID: | 20131219211807.GC1688@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Thu, Dec 19, 2013 at 01:08:18PM -0800, Sergey Konoplev wrote:
> On Thu, Dec 19, 2013 at 12:49 PM, Joseph Kregloh
> <jkregloh(at)sproutloud(dot)com> wrote:
> > On Thu, Dec 19, 2013 at 3:46 PM, Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> wrote:
> >> On Thu, Dec 19, 2013 at 12:27 PM, Joseph Kregloh
> >> <jkregloh(at)sproutloud(dot)com> 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(at)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?
pg_upgrade is looking at the data dir, the database oid, and relfilenode
to get the old path, and does the same for the new path. Tablespaces
point to the same location in old and new clusters --- only a
subdirectory PG_VERISON is different.
Is /home/jkregloh/pg_data/data also your default cluster directory? If
so, having tablespaces inside of there will not work well as they will
continue to be stored in the old cluster's data directory. Those will
not be renamed/relocated by pg_upgrade.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2013-12-19 21:24:25 | Re: pg_upgrade & tablespaces |
Previous Message | Adrian Klaver | 2013-12-19 21:16:12 | Re: pg_upgrade & tablespaces |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2013-12-19 21:24:25 | Re: pg_upgrade & tablespaces |
Previous Message | Adrian Klaver | 2013-12-19 21:16:12 | Re: pg_upgrade & tablespaces |