Search Postgresql Archives
PostgreSQL upgrade server A -> server B
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: pgsql-general@xxxxxxxxxxxxxx
- Subject: PostgreSQL upgrade server A -> server B
- From: "CAJ CAJ" <pguser@xxxxxxxxx>
- Date: Thu, 26 Apr 2007 18:09:30 -0700
- Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=uXj6grvADyLDiOSe9AIO3h2VRIZpYqapZWGrInEsCvcTrHTbH7FhrUvhg6YF3q9LHMJksoQ5WW5LjrfvmNepYrQedcpf96h7kY3t3+FOfR8zTphKd1vz3VjhQlkttvMox+R+gV5F74X9C5d0NBgzR/2/WhwXzUN6GHquaVULizA=
Hello,
Forgive me if this has been discussed before (or if it sounds absurd)
Upgrading large postgres databases (100GB+) takes awfully long time when doing dump/restore. I was wondering if this process can be optimized by directly dumping to a new version of Pg database directly on another server without having to dump to the filesystem and then restore it.
pg_dump on new server might look something like,
pg_dump <options> -h <old server> -h <new_server> dbname
or can it be used as-is by piping it?
pg_dump <options> -h <old server> dbname | pg_restore
Thanks!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]
[Postgresql Jobs]
[Postgresql Admin]
[Postgresql Performance]
[Linux Clusters]
[PHP Home]
[PHP on Windows]
[Kernel Newbies]
[PHP Classes]
[PHP Books]
[PHP Databases]
[Postgresql & PHP]
[Yosemite]