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 9AAFF533BB for ; Tue, 12 Apr 2005 13:25:24 -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 52514-06 for ; Tue, 12 Apr 2005 16:25:17 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.207]) by svr1.postgresql.org (Postfix) with ESMTP id 88FB0533B0 for ; Tue, 12 Apr 2005 13:25:09 -0300 (ADT) Received: by rproxy.gmail.com with SMTP id a41so1561202rng for ; Tue, 12 Apr 2005 09:25:08 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:reply-to:from:to:subject:date:mime-version:content-type:content-transfer-encoding:x-mailer:x-mimeole:thread-index:message-id; b=cR3xXP0ibx0mUDSac0ob1Fh3uUOx7f8XoPZO0MrEC9gikPawiyefDVaVQXJJ0CoQI3v6/+V6fqKA13tJFfrm/bbRCyEorQxXe5OACkr9tzQez0QPWo5b7g64JV5qO6DAJ8qPH9i/fhDfynxcj16tJuF9+V7oHVqoqvFBXg0Yegg= Received: by 10.38.71.62 with SMTP id t62mr4095366rna; Tue, 12 Apr 2005 09:25:08 -0700 (PDT) Received: from MATTSPC ([12.216.69.41]) by mx.gmail.com with ESMTP id h17sm1386108rnb.2005.04.12.09.25.08; Tue, 12 Apr 2005 09:25:08 -0700 (PDT) Reply-To: From: "Matthew Nuzum" To: Subject: performance hit for replication Date: Tue, 12 Apr 2005 11:25:04 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcU/fC5mJDjLLC/eTEu0T7e3ur78Ag== Message-ID: <425bf664.1fac7adf.258a.5c79@mx.gmail.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.304 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200504/236 X-Sequence-Number: 11633 I'd like to create a fail-over server in case of a problem. Ideally, it would be synchronized with our main database server, but I don't see any major problem with having a delay of up to 4 hours between syncs. My database is a little shy of 10 Gigs, with much of that data being in an archived log table. Every day a batch job is run which adds 100,000 records over the course of 3 hours (the batch job does a lot of pre/post processing). Doing a restore of the db backup in vmware takes about 3 hours. I suspect a powerful server with a better disk setup could do it faster, but I don't have servers like that at my disposal, so I need to assume worst-case of 3-4 hours is typical. 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, -- Matthew Nuzum www.followers.net - Makers of "Elite Content Management System" Earn a commission of $100 - $750 by recommending Elite CMS. Visit http://www.elitecms.com/Contact_Us.partner for details.