| From: | Tory M Blue <tmblue(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | "Nicholson, Brad (Toronto, ON, CA)" <bnicholson(at)hp(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net> |
| Subject: | Re: pg_upgrade |
| Date: | 2011-12-05 18:31:50 |
| Message-ID: | CAEaSS0ZDS8M8hQqJb2wBD8T0=VaE9DF0D9wnfeZ1wEqMMwgixQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, Dec 5, 2011 at 10:22 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>> But initial response to all this, is umm we have not really made a
>> dump/restore unnecessary with the latest releases of Postgres than, as
>> I would have to think that there is a high percentage of users whom
>> use tablespaces.
>
> Yes, but they don't change tablespace locations during the upgrade. In
> fact, we have had surprisingly few (zero) request for moving
> tablespaces, and now we are trying to implement this for Postgres 9.2.
> The normal API will be to have the user move the tablespace before the
> upgrade, but as I said before, it isn't easy to do now in Postgres.
Okay think here is where I'm confused. "they don't change tablespace",
okay how are they doing the upgrade? Do they leave the olddatadir in
the default location and create a new one elsewhere, vs where I'm kind
of doing the opposite?
Thanks again!
Tory
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2011-12-05 18:36:34 | Re: Question about VACUUM |
| Previous Message | Bruce Momjian | 2011-12-05 18:22:56 | Re: pg_upgrade |