From: | Sam Barnett-Cormack <s(dot)barnett-cormack(at)lancaster(dot)ac(dot)uk> |
---|---|
To: | Yuji Shinozaki <ys2n(at)virginia(dot)edu> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: copying databases w/ indexes |
Date: | 2003-08-14 17:58:04 |
Message-ID: | Pine.LNX.4.50.0308141857010.1651-100000@short.lancs.ac.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Thu, 14 Aug 2003, Yuji Shinozaki wrote:
>
> I have two questions about restoring and moving databases (in pg 7.3), to
> which I have not been able to find a suitable answers in the documentation
> (and searching the list archives has been painfully slow and fruitless).
>
> 1) What is the fastest way to restore a database *with indexes*?
>
> We have situation where I need to make a duplicate of a production
> database for development work, so that we can develop code without
> interfering with the production database. I use pg_dump for this, but I
> have not been able to get pg_restore to work (usually because of
> constraint problems). So I do the restores from a text dump piped into
> psql (with all the constraints applied last). Then the problem is that
> reindexing takes a very long time. One particular index is taking on the
> order of 12 hours to finish.
I've been dumping and restoring a very very big database, with indexes,
with no such problems. The table details that get dumped setup the
indexes, and AIUI the indexes are kept up-to-date as items are added.
--
Sam Barnett-Cormack
Software Developer | Student of Physics & Maths
UK Mirror Service (http://www.mirror.ac.uk) | Lancaster University
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-08-14 19:29:43 | Re: copying databases w/ indexes |
Previous Message | Yuji Shinozaki | 2003-08-14 17:35:34 | copying databases w/ indexes |