Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VKBuO-00040R-TD for pgsql-performance@arkaria.postgresql.org; Thu, 12 Sep 2013 18:46:29 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1VKBuO-0000UW-Di for pgsql-performance@arkaria.postgresql.org; Thu, 12 Sep 2013 18:46:28 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VKBuN-0000UQ-AW for pgsql-performance@postgresql.org; Thu, 12 Sep 2013 18:46:27 +0000 Received: from nm15.bullet.mail.bf1.yahoo.com ([98.139.212.174]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VKBuJ-0005mj-Bp for pgsql-performance@postgresql.org; Thu, 12 Sep 2013 18:46:26 +0000 Received: from [98.139.215.142] by nm15.bullet.mail.bf1.yahoo.com with NNFMP; 12 Sep 2013 18:46:21 -0000 Received: from [98.139.212.230] by tm13.bullet.mail.bf1.yahoo.com with NNFMP; 12 Sep 2013 18:46:21 -0000 Received: from [127.0.0.1] by omp1039.mail.bf1.yahoo.com with NNFMP; 12 Sep 2013 18:46:21 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 155053.19207.bm@omp1039.mail.bf1.yahoo.com Received: (qmail 86380 invoked by uid 60001); 12 Sep 2013 18:46:21 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ymail.com; s=s1024; t=1379011580; bh=Te8hVB5iepPFSLf1ImC0Fleedfvport3KOktu60dqy8=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=dBScHO8Fh8pnMAli6BkDyq7A8ebn6rHiVmHtyOQvDzn81j1C37UWXqeSEfoAOd6BtjH313cTRvtXtchUEpY0wfhVPTpQt2jM3URcucaEA+NTxgjJStBS9c3V1IhnBqlFLN+jdG/U1gMnJ/aGSl9rpbaeLTO9Iu7Gn2NRsqzSp0A= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=ymail.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=q7tnNrTFR4edaN6AjQgEme5sA/rHTEp/+R+rJTL5d+yj4KIKJla/VJxHG/6zMltwriV+8y7Vf3RQAe9JHATDjvWhAzB4jV0gFk7jYlTxWR1ocYE09pjAdMVYC3VnMBt2RbpRwb72/tfmdRIYjzslc2XK+0QHMeBU7gyHpD90788=; X-YMail-OSG: DILp7zkVM1lqLFBvuO9evi6QbjTeWZkXqhIGY69CoTFr9J_ t75eWI4N_2vslNfxTzmRv8YIgjBRRBZzaoWY4jc5hlpRaL6RAuvQdnyJlpg4 TJT.WgUvoJ7r4C4lkP_p8dcudlCGWhF5PyVRZEvVRcJrmUYao00q9h91zNfi 2W_H22CBLJ8qQAoOg4IiVbJazmVWWGBzYTqqquY_mTiOVIHdyPiZQeqYIKSZ ONn1_Jha1gKwZevt7yF7JbRir2ce1Ngnkg4FNVOTR1nIqvhfkR0A6XdtnZ7D EseridUQfQ4Z4nlSzdwH0U0So10Cw7HHT6O7ImwVN_ISRqkqCy8.z1gjm4k1 U5iL1aTHDVs1xxbirRA8pcLdAgeXJrKVy1hbXYlzIrwKfOXO0K_NBr8eA8N8 iJtX.Uo8OFhNpQJprGPg4at_I0fu_m9B6uwSdz01A7uDVxKQWfugp.0IhGEu M03AiIx.Akv3vLBs0Xzq7FuCgDEg4VCDte1feDhZ58WxEC2UZXu.WqdnqL3i X_X0cejH3fkMlftKNolIxlHepx4_07ZnCOSVo6UGm9dC.U4PMb.Y7ZjG60JT 9Tl0Wd9CgKWdoQkhRZh4wX1enF.BP_aVxjDG2ogOID9DG.I1sxnPI.ZuKLWi h.Q-- Received: from [76.255.18.237] by web162901.mail.bf1.yahoo.com via HTTP; Thu, 12 Sep 2013 11:46:20 PDT X-Rocket-MIMEInfo: 002.001, SmltIE5hc2J5IDxqaW1AbmFzYnkubmV0PiB3cm90ZToKCj4gSWYgeW91IHNldHVwIHNvbWUgZm9ybSBvZiByZXBsaWNhdGlvbiBpdCdzIHZlcnkgZWFzeSB0byBtb3ZlIHRvCj4gbGFyZ2VyIHNlcnZlcnMgYXMgeW91IGdyb3cuIEknbSBzdXJlIHRoYXQgd2hlbiBLZXZpbiBtb3ZlZCB0aGVpcgo.IGRhdGFiYXNlIGl0IHdhcyBhIGNvbXBsZXRlIG5vbi1ldmVudC4KClllYWgsIHJlcGxpY2F0aW9uIHdhcyB0dXJuZWQgb24gZm9yIHRoZSBuZXcgc2VydmVyIGluIGFkZGl0aW9uIHRvCnRoZSBvbGQgb25lLsKgIFcBMAEBAQE- X-Mailer: YahooMailWebService/0.8.157.561 References: <1377778443804-5768917.post@n5.nabble.com> <521F61B9.1000709@archonet.com> <521F63DD.3050301@commandprompt.com> <1377792804612-5768951.post@n5.nabble.com> <1377960241.19370.YahooMailNeo@web162901.mail.bf1.yahoo.com> <5231DB62.4080507@nasby.net> Message-ID: <1379011580.85901.YahooMailNeo@web162901.mail.bf1.yahoo.com> Date: Thu, 12 Sep 2013 11:46:20 -0700 (PDT) From: Kevin Grittner Reply-To: Kevin Grittner Subject: Re: How clustering for scale out works in PostgreSQL To: Jim Nasby Cc: bsreejithin , "pgsql-performance@postgresql.org" In-Reply-To: <5231DB62.4080507@nasby.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org Jim Nasby wrote: > If you setup some form of replication it's very easy to move to > larger servers as you grow. I'm sure that when Kevin moved their > database it was a complete non-event. Yeah, replication was turned on for the new server in addition to the old one.=A0 When everything was ready the web application configuration was updates so that it started using the new server for new requests and disconnected from the old server as requests completed.=A0 Zero down time.=A0 No user-visible impact, other than things ran a little faster because of the better hardware. One generation of old hardware is kept in replication for running ad hoc queries and to provide availability in case the new one crashes. -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company --=20 Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance