From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Postgresql 7.4 migration to (partially) new disks |
Date: | 2006-09-15 14:47:19 |
Message-ID: | 24624.1158331639@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> writes:
> What considerations should someone take if he is about to just
> cp -r <path_to_some_other_pgsql_data_path>/data .
> .i.e. creating the PGDATA dir *not* following the standard initdb procedure
If you copy the *entire* data tree (data, xlog, clog, any outside
tablespaces), and use exactly the same Postgres executables at both
ends, then it should pretty much Just Work.
> chown -R postgres:postgres ./data
> (new postgres user on the new SUSE might have a different uid/gid than the
> original Debian),
This is OK.
> I'd suppose this might work on a test system, but should someone
> rely on it for a critical production system?
As long as the DBA has practiced beforehand ;-), sure.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Frost | 2006-09-15 15:21:35 | Re: real and effective user ids must match |
Previous Message | Michael Fuhr | 2006-09-15 14:29:37 | Re: real and effective user ids must match |
From | Date | Subject | |
---|---|---|---|
Next Message | Tony Caduto | 2006-09-15 14:49:24 | Re: berkley sockets |
Previous Message | J S B | 2006-09-15 14:39:47 | Re: berkley sockets |