pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christopher Petrilli <petrilli@gmail.com>
To: Marc G. Fournier <scrappy@postgresql.org>
Cc: Matt Browne <list.pgsql-admin@picton.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: Replication in main PostgreSQL codebase
Date: Tue, 6 Jul 2004 16:41:59 -0400
Message-ID: <59d991c4040706134115dc1dd0@mail.gmail.com> (raw)
In-Reply-To: <20040706170510.W71486@ganymede.hub.org>
References: <WAITAWAZizJJamc0nTP000003e8@mail.picton.net>
	<20040706170510.W71486@ganymede.hub.org>

On Tue, 6 Jul 2004 17:07:33 -0300 (ADT), Marc G. Fournier
<scrappy@postgresql.org> 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



view thread (12+ messages)  latest in thread

Message-ID: <59d991c4040706134115dc1dd0@mail.gmail.com>
Permalink:  ../59d991c4040706134115dc1dd0@mail.gmail.com/
Also on:    postgresql.org/message-id/59d991c4040706134115dc1dd0@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: petrilli@gmail.com, scrappy@postgresql.org, list.pgsql-admin@picton.net
  Subject: Re: Replication in main PostgreSQL codebase
  In-Reply-To: <59d991c4040706134115dc1dd0@mail.gmail.com>
  References: <WAITAWAZizJJamc0nTP000003e8@mail.picton.net> <20040706170510.W71486@ganymede.hub.org> <59d991c4040706134115dc1dd0@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox