| From: | Joseph Kregloh <jkregloh(at)sproutloud(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)gmail(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: | 2013-12-31 21:51:22 |
| Message-ID: | CAAW2xfdHWixFpvWm294S8BimZET-kGw=C5XUh+OZirmKydVAsA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
>
> So you have not upgraded the tablespaces. What is important to remember is
>> Postgres uses numbers to keep track of relations. Part of the upgrade
>> process involves changing the numbers that point at relations. By manually
>> dropping a 9.0 tablespace into a 9.3 data directory you have broken that
>> system. You need to let pg_upgrade do the translation. See my previous
>> message below for a possible solution:
>>
>
>
Sorry, I may not have been to clear on my explenation, pg_upgrade creates
the 9.3 data directories inside the tablespace folders and those are the
ones I moved. So pg_upgrade finishes it's job.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2013-12-31 22:02:59 | Re: pg_upgrade & tablespaces |
| Previous Message | Adrian Klaver | 2013-12-31 21:39:08 | Re: pg_upgrade & tablespaces |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2013-12-31 21:56:53 | Re: Patch: show relation and tuple infos of a lock to acquire |
| Previous Message | Mark Dilger | 2013-12-31 21:51:08 | Re: proposal: multiple read-write masters in a cluster with wal-streaming synchronization |