Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 781A29F9EE6 for ; Fri, 19 Oct 2007 15:30:18 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 98209-09 for ; Fri, 19 Oct 2007 15:30:13 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by postgresql.org (Postfix) with ESMTP id 73FF79F9E31 for ; Fri, 19 Oct 2007 15:30:11 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id j3so646653ugf for ; Fri, 19 Oct 2007 11:30:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=Wnxf11JXieun8pHP1tjZuUTZf6Gtmh3d9vBgXXXw12M=; b=eYwv5udINOC3YR/qyjCCMpTjWccoKvvPgNGXhoX2kXO1MGkLc6SAR9xjROgmmyoqofq+bq2n+RGx0V/zVPVlZQMsHWln7m35DOcnUn3idDG3qBe0UGjGR5wXA4hm4FCz7hK4V/nR9cTTKkp9FJfYm5YaaFkrqbIEkmq8MbSz0Uo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=eNlYFLRf87ZcbmR5CcJsRWRVXgREK3eOhFUA1YcvzzvYii9MvIFi7kLHrRv2pfwfWuawV1fAPIPe7bwoiFp02Y0ZFJ/UXWIvt4otxhiyVkftxcIO4rKf19SNoCJWfR1Jhb/wIs5UEQE2H8pOwmiEM3PS1Q1/RXuOidgRpqppZEw= Received: by 10.67.25.6 with SMTP id c6mr3327223ugj.1192818610244; Fri, 19 Oct 2007 11:30:10 -0700 (PDT) Received: by 10.67.29.6 with HTTP; Fri, 19 Oct 2007 11:30:10 -0700 (PDT) Message-ID: Date: Fri, 19 Oct 2007 13:30:10 -0500 From: "Scott Marlowe" To: "Joshua D. Drake" Subject: Re: Cluster/Replication Cc: "Sean Brown" , pgsql-admin@postgresql.org In-Reply-To: <20071019100626.09fd9e13@scratch> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20071019100626.09fd9e13@scratch> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/196 X-Sequence-Number: 27110 On 10/19/07, Joshua D. Drake wrote: > On Fri, 19 Oct 2007 12:43:40 -0400 > Sean Brown wrote: > > > I believe this has come up before, and I am still researching how to > > do this and figured asking was probably a good idea as hopefully I > > can either get some direction or someone can point me at something I > > haven't seen yet. > > Why do you have a synchronous requirement? He said something about losing any data due to the loss of the master being unacceptable, so synchronous was the only way to go. But if the machines are separated by any real distance, the speed / latency of the link will be the deciding factor in the write performance of the whole system. I think they might be better off having a local synchronous clustering solution (i.e. two machines running in failover on shared storage or something) and then async rep cross country if there's any distance to the other server. What to do about slony not handling LOBs I don't know.