From: | Joseph Kregloh <jkregloh(at)sproutloud(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Sergey Konoplev <gray(dot)ru(at)gmail(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:55:34 |
Message-ID: | CAAW2xff7OCKypO0Et74Mof9X3w+78KUndiVaD4kc0LKMoK2FyA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Thu, Dec 19, 2013 at 4:18 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> 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.
>
>
No, that is not my default cluster dir. That is just the data directory of
my 9.0 install that I mounted there in order to do the pg_upgrade.
Essentially that points to /usr/local/pgsql/data on my 9.0 jail.
> --
> Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
> EnterpriseDB http://enterprisedb.com
>
> + Everyone has their own god. +
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2013-12-19 23:19:32 | Re: pg_upgrade & tablespaces |
Previous Message | Joseph Kregloh | 2013-12-19 21:52:29 | Re: pg_upgrade & tablespaces |
From | Date | Subject | |
---|---|---|---|
Next Message | Sergey Konoplev | 2013-12-19 22:37:04 | Hot standby 9.2.6 -> 9.2.6 PANIC: WAL contains references to invalid pages |
Previous Message | Joseph Kregloh | 2013-12-19 21:52:29 | Re: pg_upgrade & tablespaces |