On Wed, Aug 27, 2014 at 09:05:41AM -0400, Robert Haas wrote: > Another idea is to have a command that you can run, while connected to > a particular database, that updates the default tablespace for that > database without actually moving any data on disk - i.e. it sets > pg_database.dattablespace, and then updates every pg_class row where > reltablespace = 0 to the old default tablespace, and pg_class row > where reltablespace = the new tablespace ID to 0. Then you can move > individual relations afterwards if you feel like it. But that might > still require a lot of locks, and I think we also have a limitation > that some relations (the mapped ones?) have to be in the database's > default tablespace, which obviously wouldn't work here. > > So it's a tricky problem.
Is there a doc patch to make here? -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
