public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: Jim C. Nasby <[email protected]>
Cc: Dawid Kuroczko <[email protected]>
Cc: [email protected]
Cc: [email protected]
Subject: Re: [HACKERS] Replication documentation addition
Date: Thu, 26 Oct 2006 15:41:39 -0400 (EDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

Jim C. Nasby wrote:
> On Thu, Oct 26, 2006 at 11:59:57AM -0400, Bruce Momjian wrote:
> > Jim C. Nasby wrote:
> > > On Wed, Oct 25, 2006 at 08:42:07PM -0400, Bruce Momjian wrote:
> > > > Jim C. Nasby wrote:
> > > > > Something else worth doing though is to have a paragraph explaining why
> > > > > there's no built-in replication. I don't have time to write something
> > > > > right now, but I can do it later tonight if no one beats me to it.
> > > > 
> > > > I thought that was implied in the early paragraph about why there are
> > > > many solutions.
> > > 
> > > I think we should explicitely spell it out, especially considering how
> > > many times people ask about it. How about...
> > > 
> > >  This multitude of choices is why PostgreSQL does not ship with a
> > >  replication solution by default; any bundled solution would only
> > >  satisfy a subset of replication needs.
> > 
> > The problem is that we do have some solutions in our code, like doing
> > data partitioning in the application, warm standby, or using a shared
> > disk for failover, so how do we spell that out?  I say there are
> > multiple solutions, but I don't see how I can say that all are external
> > and not included.
> 
> Good point... how about this?

Sorry, that is too preachy, and I have the extensibility issue addressed
in the commerical solutions section.

-- 
  Bruce Momjian   [email protected]
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

view thread (117+ messages)  latest in thread

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 using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: [HACKERS] Replication documentation addition
  In-Reply-To: <[email protected]>

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

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