| From: | John R Pierce <pierce(at)hogranch(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pg_upgrade & tablespaces |
| Date: | 2013-12-19 21:14:15 |
| Message-ID: | 52B361A7.1040302@hogranch.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On 12/19/2013 1:06 PM, Joseph Kregloh wrote:
> It's easier to keep things segregated. It is not anymore different
> than doing the upgrade in the same jail. Which at the end of the day
> you are doing the upgrade in the same jail, because at the end of the
> day pg_upgrade just needs the old data an binary to start and create
> some dump files.
pg_upgrade needs to access the old data AND all the tablespaces at the
same paths as the old server sees them AND the new data and tablespaces
at the same path as the NEW server sees them. if the two servers are
in different jails, I don't see how you could make that work... if you
run pg_upgrade in the host system, then all the paths are different for
both sets of data and tablespaces.
--
john r pierce 37N 122W
somewhere on the middle of the left coast
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anand Kumar, Karthik | 2013-12-19 21:15:31 | Re: index and table corruption |
| Previous Message | Sergey Konoplev | 2013-12-19 21:08:18 | Re: pg_upgrade & tablespaces |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2013-12-19 21:16:12 | Re: pg_upgrade & tablespaces |
| Previous Message | Bruce Momjian | 2013-12-19 21:11:44 | Re: clang's -Wmissing-variable-declarations shows some shoddy programming |