Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id D81A01337BA3 for ; Tue, 19 Oct 2010 12:17:25 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 92269-03 for ; Tue, 19 Oct 2010 15:17:17 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.9]) by mail.postgresql.org (Postfix) with ESMTP id 972061337BA6 for ; Tue, 19 Oct 2010 12:17:17 -0300 (ADT) Received: from [192.168.1.7] (static-71-179-240-8.bltmmd.fios.verizon.net [71.179.240.8]) by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis) id 0MARW2-1OxkKr1D46-00Br0P; Tue, 19 Oct 2010 17:16:56 +0200 Message-ID: <4CBDB665.60408@2ndquadrant.com> Date: Tue, 19 Oct 2010 11:16:53 -0400 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Josh Berkus CC: postgres hackers Subject: Re: Simplifying replication References: <4CBCE356.2080703@agliodbs.com> In-Reply-To: <4CBCE356.2080703@agliodbs.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:guW4VUk8UiR5HsLw1+zjDVtwbUSA6X8XkttALUbcFTL sa3TyeYH0/dpMTgYFAz5D+Mtxr7srCvnhM7Lt++IVnlYqvvz5P g+/KnZeQCj3rDzThiU14ByJFMX3EQxtCHvs4w28S/PR0XsA/3V ZDNYUQaiqOL+fJ5HBDu7W6VxP6MtQ3UHpoTIyMoRQZbX573qhv grrrd4fHFaavfGG6FFOnj+B8UUYY5Nk0h0EQsVIxnc= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=2.419 tagged_above=-5 required=5 tests=BAYES_00=-1.9, FS_REPLICA=3.599, RCVD_IN_DNSWL_NONE=-0.0001, SARE_SPEC_REPLICA=0.72 X-Spam-Level: ** X-Archive-Number: 201010/1302 X-Sequence-Number: 172342 Josh Berkus wrote: > It is critical that we make replication easier to set up, administrate > and monitor than it currently is. In my conversations with people, > this is more important to our users and the adoption of PostgreSQL > than synchronous replication is. You should enjoy one of the patches we're furiously working on then, which is aiming at some of the administration and monitoring pieces here. I have my own grand vision of how easy replication should be to setup too. Visions and plans are nice, but building functional pieces of them and delivering them to the community is what actually moves PostgreSQL forward. So far, multiple people have done that for sync rep, and what we're supposed to be focused on at this stage in the development cycle is finishing the work related to the open CommitFest item that includes that. I find this launch into a new round of bike-shedding a bit distracting. If you want this to be easier to use, which it's obvious to any observer it should be because what's delivered in 9.0 is way too complicated, please work on finding development resources to assign to that problem. Because that's the bottleneck on simplifying things, not ideas about what to do. I would recommend finding or assigning a developer to work on integrating base backup in to the streaming protocol as the biggest single thing that would improve the built-in replication. All of the rest of the trivia about what knobs to set and such are tiny details that make for only a minor improvement until that's taken care of. -- Greg Smith, 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services and Support www.2ndQuadrant.us