X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id F1ED5D1D6CC for ; Wed, 14 Apr 2004 06:12:58 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 15345-09 for ; Wed, 14 Apr 2004 06:12:59 -0300 (ADT) Received: from curie.credativ.org (credativ.com [217.160.209.18]) by svr1.postgresql.org (Postfix) with ESMTP id 32786D1D1B8 for ; Wed, 14 Apr 2004 06:12:57 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by curie.credativ.org (Postfix) with ESMTP id AF67C55BEB; Wed, 14 Apr 2004 11:12:58 +0200 (CEST) Received: from colt.pezone.net (dsl-213-023-254-104.arcor-ip.net [213.23.254.104]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by curie.credativ.org (Postfix) with ESMTP id 3B8B355BE8; Wed, 14 Apr 2004 11:12:58 +0200 (CEST) From: Peter Eisentraut To: Christopher Browne , pgsql-admin@postgresql.org Subject: Re: Real time replication of PG DBs accross two servers - any experiences? Date: Wed, 14 Apr 2004 11:12:57 +0200 User-Agent: KMail/1.5.1 References: <407B85CF.4010404@kieser.net> <200404132052.12589.peter_e@gmx.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200404141112.57204.peter_e@gmx.net> X-Virus-Scanned: by AMaViS at credativ.com X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/213 X-Sequence-Number: 13186 Christopher Browne wrote: > > To ensure high availability, using DRBD to replicate the storage or > > using a shared storage (e.g., EMC^2) does the job. That saves you > > the trouble of having to set up and manage a database replication > > solution at all. > > Regrettably, "disk replication" schemes aren't generally able to cope > with keeping the database up and alive while replication is taking > place. The ones mentioned above certainly keep the database running at all times until a failover. > You need to shut down the database that is attached to a > "target/slave" system every time you "sync" the target/slave against > the source/master. The slave database doesn't run at all while the master is alive. > But when the people paying for the duplicate set of hardware realize > that it's sitting there "otherwise useless" at any time that there > hasn't been a failure, they'll presumably agitate for some 'better' > sort of replication... If you can set up a true database-level replication system that does something useful with the slave server while the master is running (i.e., load balancing) for the same price (hardware + labor + post-installation service) that you (or I or someone) can set up a disk replication system for then it would be interesting. So far I haven't seen it happening. In my experience, load balancing is not needed in most cases, so no one is going to bother paying for the extra functionality that they don't need. The other advantage of disk replication is that you can secure almost any service in that same way (web, dns, ldap, etc.), so the management and setup effort spent on any particular service diminishes.