X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 2094053B15 for ; Tue, 12 Apr 2005 18:04:18 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 46588-04 for ; Tue, 12 Apr 2005 21:04:08 +0000 (GMT) Received: from floppy.pyrenet.fr (floppy.pyrenet.fr [194.116.145.2]) by svr1.postgresql.org (Postfix) with ESMTP id D477853A77 for ; Tue, 12 Apr 2005 18:04:07 -0300 (ADT) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id 2F0C630952; Tue, 12 Apr 2005 23:03:26 +0200 (MET DST) From: Chris Browne X-Newsgroups: pgsql.performance Subject: Re: performance hit for replication Date: Tue, 12 Apr 2005 16:25:14 -0400 Organization: cbbrowne Computing Inc Lines: 31 Message-ID: <60d5szu4id.fsf@dba2.int.libertyrms.com> References: <425bf664.1fac7adf.258a.5c79@mx.gmail.com> <425BF92D.6060004@commandprompt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Jumbo Shrimp, linux) Cancel-Lock: sha1:+3C1/OuQuTH45Vfl0T2PjyL7AaU= To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.172 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200504/243 X-Sequence-Number: 11640 jd@commandprompt.com ("Joshua D. Drake") writes: >>So, my question is this: My server currently works great, >>performance wise. I need to add fail-over capability, but I'm >>afraid that introducing a stressful task such as replication will >>hurt my server's performance. Is there any foundation to my fears? I >>don't need to replicate the archived log data because I can easily >>restore that in a separate step from the nightly backup if disaster >>occurs. Also, my database load is largely selects. My application >>works great with PostgreSQL 7.3 and 7.4, but I'm currently using >>7.3. >> >>I'm eager to hear your thoughts and experiences, >> > Well with replicator you are going to take a pretty big hit > initially during the full sync but then you could use batch > replication and only replicate every 2-3 hours. > > I am pretty sure Slony has similar capabilities. Yes, similar capabilities, similar "pretty big hit." There's a downside to "batch replication" that some of the data structures grow in size if you have appreciable periods between batches. -- (format nil "~S@~S" "cbbrowne" "acm.org") http://www.ntlug.org/~cbbrowne/slony.html Rules of the Evil Overlord #78. "I will not tell my Legions of Terror "And he must be taken alive!" The command will be: ``And try to take him alive if it is reasonably practical.''"