From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
---|---|
To: | Joseph Kregloh <jkregloh(at)sproutloud(dot)com> |
Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, John R Pierce <pierce(at)hogranch(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_upgrade & tablespaces |
Date: | 2014-01-10 16:53:17 |
Message-ID: | 52D0257D.2000501@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On 01/10/2014 08:40 AM, Joseph Kregloh wrote:
> Just as a followup to this. The process that I am using to do the
> upgrade is as follows:
>
> 1. Install Postgres 9.3 in /opt dir.
> 2. In 9.0 instance update spclocation in pg_tablespace.
> 3. Update the symlinks in the pg_tblspace folder.
> 4. Move the tablespace folders to new location.
> 5. Run pg_upgrade.
> 6. Test upgrade results on 9.3 cluster.
> 7. Run the sh files created by pg_upgrade.
> 8. Uninstall Postgres 9.3 in /opt dir.
> 9. Install Postgres 9.3 in default location.
> 10. Enjoy Postgres 9.3.
For completeness, the new location you are moving the tablespaces to, is
that in or out of $PGDATA?
FYI, from comments over on --hackers, I believe Bruce Momjian may offer
some insight on what is going on.
>
> I could actually move the 9.0 cluster after moving the table spaces and
> install 9.3 in the default location as the documentation shows. But I
> haven't experimented with that scenario yet.
>
> -Joseph
>
>
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | gator_ml | 2014-01-10 17:03:13 | Re: Consistent file-level backup of pg data directory |
Previous Message | Joseph Kregloh | 2014-01-10 16:40:55 | Re: pg_upgrade & tablespaces |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2014-01-10 17:07:20 | Re: Add CREATE support to event triggers |
Previous Message | Tom Lane | 2014-01-10 16:46:33 | Re: [PATCH] Negative Transition Aggregate Functions (WIP) |