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 10611D1E122 for ; Tue, 13 Apr 2004 15:52:30 -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 41839-08 for ; Tue, 13 Apr 2004 15:52:28 -0300 (ADT) Received: from curie.credativ.org (credativ.com [217.160.209.18]) by svr1.postgresql.org (Postfix) with ESMTP id 130A4D1DC7D for ; Tue, 13 Apr 2004 15:52:27 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by curie.credativ.org (Postfix) with ESMTP id 1E64C55BEB; Tue, 13 Apr 2004 20:52:28 +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 0755D55BE8; Tue, 13 Apr 2004 20:52:24 +0200 (CEST) From: Peter Eisentraut To: Bradley Kieser , pgsql-admin@postgresql.org Subject: Re: Real time replication of PG DBs accross two servers - any experiences? Date: Tue, 13 Apr 2004 20:52:12 +0200 User-Agent: KMail/1.5.1 References: <407B85CF.4010404@kieser.net> In-Reply-To: <407B85CF.4010404@kieser.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200404132052.12589.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/207 X-Sequence-Number: 13180 Bradley Kieser wrote: > I desperately need to set up a real time replication of several > databases (for failover) between two servers. Last time I looked at > the PG replication it wasn't yet production level. I wonder if anyone > on this list is doing this successfully and if you won't mind sharing > your experience and giving me any tips that you may think would be > handy from a real world perspective I would very much appreciate it. 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.