Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YXrhg-00059t-1k for pgsql-admin@arkaria.postgresql.org; Tue, 17 Mar 2015 13:38:40 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YXrhf-0004C1-H6 for pgsql-admin@arkaria.postgresql.org; Tue, 17 Mar 2015 13:38:39 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YXrhe-0004Bu-Du for pgsql-admin@postgresql.org; Tue, 17 Mar 2015 13:38:38 +0000 Received: from mail-wi0-x22e.google.com ([2a00:1450:400c:c05::22e]) by magus.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1YXrha-00082f-5K for pgsql-admin@postgresql.org; Tue, 17 Mar 2015 13:38:37 +0000 Received: by wibg7 with SMTP id g7so47048795wib.1 for ; Tue, 17 Mar 2015 06:38:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:subject:from:reply-to:to:cc:date:in-reply-to:references :content-type:mime-version:content-transfer-encoding; bh=qAa2mXBeJmixmot+DZwCb31i1vkZGwl7wjjYYSHduv0=; b=fUaRXoG1pbvIn0G2PG+J5DhujnrvD3NY9BhKC2zIeM994waFDKmRrOVkiUBaVBjfiN +v0DoJPNfGgAjQC4oEcbj85ozH2TJM6sEtsU6hSEEQeSVF/yYLFq/ockskHasOmirs/N ONMbc6AlViUoqe0uSiuPd14+pkV46+4/q5KcbJsCZlYmVcegWeETpSSv5AEGizk3UvJ3 iveBdaIvlqtgSrXQ2Qk+ypzhcJx/gmQQt4HT3QtQVftgFZbSkTXnPT7Va2INnqLZYODM 2Tyla051ouoow209A6WUXscIhKXu1SyzJefB+Rjp55vNZv1T5iM8DmDWYWPiZ0XPqZoF 0gVQ== X-Received: by 10.194.223.5 with SMTP id qq5mr135544069wjc.152.1426599512818; Tue, 17 Mar 2015 06:38:32 -0700 (PDT) Received: from enterprisedb01 (84.125.177.156.dyn.user.ono.com. [84.125.177.156]) by mx.google.com with ESMTPSA id gj16sm2722484wic.24.2015.03.17.06.38.31 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Mar 2015 06:38:31 -0700 (PDT) Message-ID: <1426599508.18267.11.camel@gmail.com> Subject: Re: pgpool + BDR, is it possible? From: jaime soler Reply-To: jaime.soler@gmail.com To: Craig Ringer Cc: Ruth Melendo , pgsql-admin Date: Tue, 17 Mar 2015 14:38:28 +0100 In-Reply-To: References: <001801d05fef$e8dca0a0$ba95e1e0$@teltronic.es> <005701d06081$c8acf450$5a06dcf0$@teltronic.es> <007801d06093$5abd0360$10370a20$@teltronic.es> <008d01d06098$2d706320$88512960$@teltronic.es> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.10-0ubuntu1~14.10.1 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org El mar, 17-03-2015 a las 21:03 +0800, Craig Ringer escribió: > > On 17 March 2015 at 17:52, Ruth Melendo wrote: > > But now, my dude is about pgpool. Do you think It can work > well just as a balancer in this environment? > > > > > I cannot tell you that with any confidence without knowing more about > the application than is going to be practical. The best I can do is > "probably, with the caveats already explained re async multi-master > above". > > > My main troubles from the beginning have been in recovery and > I dind´t find detailed doc in that way. Most of times, I need > to delete data directory in node 2 and starts init replication > again. > > > > > "recovery" from what? What are you trying to do? I think, she means failback master-master cluster after any node have had an error and postgresql was stopped in that node. > > > -- > Craig Ringer http://www.2ndQuadrant.com/ > PostgreSQL Development, 24x7 Support, Training & Services > -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin