Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 151A66330C4 for ; Mon, 16 Feb 2009 15:52:49 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 35240-03 for ; Mon, 16 Feb 2009 15:52:38 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-gx0-f224.google.com (mail-gx0-f224.google.com [209.85.217.224]) by mail.postgresql.org (Postfix) with ESMTP id 52E4E633098 for ; Mon, 16 Feb 2009 15:52:38 -0400 (AST) Received: by gxk24 with SMTP id 24so4311452gxk.19 for ; Mon, 16 Feb 2009 11:52:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=Ak33DFsEghhVs1TIbFKcrTD/UNV0kFdNj26SC/chQhs=; b=YMVmlaW+3tgG42MHb/4cMrZOTmRMmtBlR1DbZg2ra7g1z3HkDLGofRcTQuQpnynffQ 0MZxpuvRAHPETmN+dbbUb826VCrNunwMZ2tVPD7VJ2K6/k2vbfIv2AssNx+5i8yyIjIa ajcYyG51g17St8kHqVQtx9KRvBWPE31QnRb0U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=kl3u1PxEze1hbQI6lidNqh/10hGnhwfRWST+TnUV7leaeMnLH9z9CUp9suXiA6P+vz ofcX27icDoMeInN2QxAMZ+UT4jch8Gf38ldTKmjWtdIGuJhoRuUVuVi5d1Nn+MsUSd7e vpTn9OJlXLWR8qIpiPak1CQpjkAdytVhLKNIw= MIME-Version: 1.0 Received: by 10.150.143.12 with SMTP id q12mr2950499ybd.105.1234813957366; Mon, 16 Feb 2009 11:52:37 -0800 (PST) Date: Mon, 16 Feb 2009 16:52:37 -0300 Message-ID: <3a0028490902161152l13cc82eva6b26c013776cbcf@mail.gmail.com> Subject: Downtime From: Rafael Domiciano To: "pgsql-admin@postgresql.org" Content-Type: multipart/alternative; boundary=000e0cd56aa44ae3ab04630e8724 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200902/105 X-Sequence-Number: 31326 --000e0cd56aa44ae3ab04630e8724 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hello for all, Our bussiness do not tolerate anymore downtime (the downtime is estimate at 10 hour / year - that involves upgrade of hardware, crash of hardware), and using Slony-I 1.2.15 I have waste time to put the slave node on production. So I'm studying some replications softwares, like pgpool, pg_cluster, pg_replicator. Pgpool has a good idea, I can connect at 2 servers or more at the same time. But I have some limitations, like Replication, Datas generated by the servers (CURRENT_DATE, CURRENT_TIME, serial, oid); so I discarded it. I tryed pg_cluster, but the documentation is very poor, and the installation was unsuccesfull. I would like to know from you what solution you uses for avoiding downtime, so I could choose the solution that is best to my scenario and for others that is begining in Postgres and is a little lost in replication. Thnks for all, Rafael Domiciano DBA Postgres --000e0cd56aa44ae3ab04630e8724 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hello for all,

Our bussiness do not tolerate anymore downtime (the downtime is estimate at 10 hour / year - that involves upgrade of hardware, crash of hardware), and using Slony-I 1.2.15 I have waste time to put the slave node on production.
So I'm studying some replications softwares, like pgpool, pg_cluster, pg_replicator.

Pgpool has a good idea, I can connect at 2 servers or more at the same time. But I have some limitations, like Replication, Datas generated by the servers (CURRENT_DATE, CURRENT_TIME, serial, oid); so I discarded it.
I tryed pg_cluster, but the documentation is very poor, and the installation was unsuccesfull.

I would like to know from you what solution you uses for avoiding downtime, so I could choose the solution that is best to my scenario and for others that is begining in Postgres and is a little lost in replication.

Thnks for all,

Rafael Domiciano
DBA Postgres --000e0cd56aa44ae3ab04630e8724--