X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 00255D1B1DA for ; Tue, 6 Jul 2004 17:42:29 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 61410-10 for ; Tue, 6 Jul 2004 20:42:27 +0000 (GMT) Received: from mproxy.gmail.com (mproxy.gmail.com [216.239.56.247]) by svr1.postgresql.org (Postfix) with SMTP id D454ED1B190 for ; Tue, 6 Jul 2004 17:42:23 -0300 (ADT) Received: by mproxy.gmail.com with SMTP id w29so3469464cwb for ; Tue, 06 Jul 2004 13:42:13 -0700 (PDT) Received: by 10.11.118.71 with SMTP id q71mr493299cwc; Tue, 06 Jul 2004 13:41:59 -0700 (PDT) Message-ID: <59d991c4040706134115dc1dd0@mail.gmail.com> Date: Tue, 6 Jul 2004 16:41:59 -0400 From: Christopher Petrilli To: "Marc G. Fournier" Subject: Re: Replication in main PostgreSQL codebase Cc: Matt Browne , pgsql-admin@postgresql.org In-Reply-To: <20040706170510.W71486@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20040706170510.W71486@ganymede.hub.org> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200407/73 X-Sequence-Number: 14141 On Tue, 6 Jul 2004 17:07:33 -0300 (ADT), Marc G. Fournier wrote: > It would be unwise for *anyone* to state "never" as far as inclusion of > built-in replication, but since the general consensus is that there is no > such thing as the 'all-encompassing solution' for this, the chances of one > ever coming about that would be of a scope that would be acceptable to be > built-in is next to zero ... I think what I run into is that while most of us would agree that the "one size fits all" argument is useless from a technical perspective, it's not the technical people that are usually the ones involved here. From a "marketing" perspective, it would be useful if PostgreSQL included at least a single master, single slave replication model that was easily enabled and set up. There is a subclass of the problem that is common to most situations, which is the ability to have a "live" backup. Perhaps the 'dbmirror' component in the 'contrib' directory is enough, and it simply needs to be highlighted. It does meet some subset of the needs out there. Sadly, a lot of problems are simply marketing perceptions :/ Chris -- | Christopher Petrilli | petrilli@gmail.com