| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, rob stone <floriparob(at)gmail(dot)com>, Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>, pgsql-general(at)postgresql(dot)org, myon(at)debian(dot)org |
| Subject: | Re: Running pg_upgrade under Debian |
| Date: | 2015-04-20 22:09:00 |
| Message-ID: | 20150420220900.GE11725@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Apr 20, 2015 at 07:06:37PM -0300, Alvaro Herrera wrote:
> ISTM there's a documentation bug here: in the code, the "dump" method
> checks for tablespaces and raises an error if they are found, but the
> "upgrade" method does not check. I think the documentation should state
> that only the dump method does not support tablespaces.
OK, it would be nice if someone could report that to upstream Debian. I
am a little confused why pg_dump/pg_restore can't use tablespaces
though. Years ago we used to not use PG-major-version-specific
subdirectories in tablespaces, but we added that for pg_upgrade, and I
am sure they would work fine for pg_dump too.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-04-20 22:18:12 | Re: Running pg_upgrade under Debian |
| Previous Message | Alvaro Herrera | 2015-04-20 22:06:37 | Re: Running pg_upgrade under Debian |