-----BEGIN PGP SIGNED MESSAGE-----
Chris Hoover wrote:
>>> 2. copy whole data directory over to new SAN
>> If database is big, then I think that is much faster to copy running
>> to new SAN.
>> Then stop postgres and rsync what was changed - but this will be probably
>> only a few files.
> I believe if you do this, you will not get a function database in the end.
> There is a lot of data that is held in memory/buffers that may not be
> flushed to the disks. You have no guarantee you will get this data with
> this method.
The method would work if they are willing to have an outage. Basically
you do an initial rsync of the large db...
Then you shut down the db.
And rsync again, which will be faster than doing a complete move with
The key here is, if you use this method... there is *zero* way around
shutting down the database before the second rsync.
Joshua D. Drake
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/
UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
In response to
pgsql-admin by date
|Next:||From: xmuinn||Date: 2007-09-21 01:20:05|
|Subject: How to repair if file pg_clog/0000 is deleted|
|Previous:||From: Chris Hoover||Date: 2007-09-20 18:10:11|
|Subject: Re: Moving database install to new SAN|