On Wed, 10 Jul 2013, Vincent Lau wrote:
On Wed, Jul 10, 2013 at 12:19 PM, Wells Oliver <wellsoliver@xxxxxxxxx>wrote:
OK, cool. I did not want to be in a position where I stop the servers,
pg_upgrade --link 9.1 to 9.2, then (eventually) pg_dropcluster of 9.1 and,
woops, I killed all of my data files.
And if you have enough storage, you can always stage a testing environment
and test this out. It'd tell you how long the whole upgrade would take too.
:)
On Wed, Jul 10, 2013 at 12:13 PM, ktm@xxxxxxxx <ktm@xxxxxxxx> wrote:
On Wed, Jul 10, 2013 at 12:02:06PM -0700, Wells Oliver wrote:
Hard linking means that you must maintain 8.2's data directory though,
even
after upgrade, correct? Since it's a link and not a copied file.
I think it only hard links the files to the new 9.2 data directory so you
can delete the old data directory and the files will still be in the new
directory since the link count will be > 0.
Ken
--
Wells Oliver
wellsoliver@xxxxxxxxx
--
Vincent Lau | Database Administrator
503.284.7581 x394 | vincent.lau@xxxxxxxxxxx <vincent.lau@xxxxxxxxxxxxxxx>
RENTRAK | www.rentrak.com | NASDAQ: RENT
Notice: This message is confidential and is intended only for the
recipient(s) named above. If you have received this message in error,
or are not the named recipient(s), please immediately notify the
sender and delete this message.
how would pg_upgrade be used to upgrade to a new machine
use nfs?
would i run pg_upgrade on the new server?
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
