Thank John,
I was naive hoping I just had to run "$ psql -f pgdumpall.output postgres"...
but it makes sense since the drive on which it is all stored won't be there anymore.
So let's read initdb documentation :-)
Daniel
-----Original Message-----
From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of John R Pierce
Sent: May-13-15 14:16
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Restarting DB after moving to another drive
On 5/13/2015 11:06 AM, Daniel Begin wrote:
> I am then currently running pg_dumpall on the database. I will restore the cluster on the new drive once completed.
However,there is still something obscure in the process. The doc says "pg_dumpall requires all needed tablespace
directoriesto exist before the restore". External tablespaces directories are easy to create but what's about
pg_defaultand pg_global tablespace since I never created specific tablespaces for them?
those are created when you initdb the target cluster prior to restoring the pg_dumpall output.
--
john r pierce, recycling bits in santa cruz
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
