Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id ECC9D9FA1CE for ; Thu, 20 Sep 2007 15:10:16 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 56038-04 for ; Thu, 20 Sep 2007 15:10:12 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by postgresql.org (Postfix) with ESMTP id 2594B9F9A66 for ; Thu, 20 Sep 2007 15:10:13 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id j3so462764ugf for ; Thu, 20 Sep 2007 11:10:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=WYD8fhgSMHGsKKKQfTIsN4XlD9QACLt6rg2pfRecGmo=; b=GjAviXpNeFG530DiEPv2l+N8x1sAJKIKsXDMoEJyQT2U24qVIcgZWUI/YXPjpu2Gj69CklAmU7unUTfWTebU71EIEzjReieZMKZEIDUVF0q3SJwkp7qFmmewyq5fQBZhBrjzdnkQBkeZJM04m/0QlXDysMFVphCp18mfRiQX2hw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=c94dC5LvTVDIyRDXXIbO7zHnihIazO9b85NmsAM/xkMnAHvlAJ7SEPSemdZkW6fpg4AwV+nPrO+j6+6o8hJCKljKklNFAJCGTm9nqoQtB/oEClKdpl+qjdIRGfC49TNpdM4Zln1va3WBGKOpjNf8907cd6z9Hqb02Yzk1+++bHw= Received: by 10.78.159.7 with SMTP id h7mr1455713hue.1190311811999; Thu, 20 Sep 2007 11:10:11 -0700 (PDT) Received: by 10.78.201.16 with HTTP; Thu, 20 Sep 2007 11:10:11 -0700 (PDT) Message-ID: <1d219a6f0709201110r603e1d4dg8cc4f514201a65ab@mail.gmail.com> Date: Thu, 20 Sep 2007 14:10:11 -0400 From: "Chris Hoover" To: "Andrzej Zawadzki" Subject: Re: Moving database install to new SAN Cc: pgsql-admin@postgresql.org In-Reply-To: <46E9A81D.90309@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_31894_8415147.1190311811995" References: <507905.14268.qm@web57114.mail.re3.yahoo.com> <20070913203946.GE6423@easy2.in-chemnitz.de> <46E9A81D.90309@gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200709/128 X-Sequence-Number: 26889 ------=_Part_31894_8415147.1190311811995 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline > > > 2. copy whole data directory over to new SAN > If database is big, then I think that is much faster to copy running > database > 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. Either shut the database down and cold copy it, or setup replication using Slony to move the data in a "hot"mode. HTH, Chris ------=_Part_31894_8415147.1190311811995 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

> 2. copy whole data directory over to new SAN
If database is big, then I think that is much faster to copy running
database
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.

Either shut the database down and cold copy it, or setup replication using Slony to move the data in a "hot"mode.

HTH,

Chris

------=_Part_31894_8415147.1190311811995--