Re: Core team statement on replication in PostgreSQL - Mailing list pgsql-hackers

From Chris Browne
Subject Re: Core team statement on replication in PostgreSQL
Date
Msg-id 60bq2o22a8.fsf@dba2.int.libertyrms.com
Whole thread Raw
In response to Re: Core team statement on replication in PostgreSQL  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
tgl@sss.pgh.pa.us (Tom Lane) writes:
> As I said originally, we have no expectation that the proposed features
> will displace the existing replication projects for "high end"
> replication problems ... and I'd characterize all of Robert's concerns
> as "high end" problems.  We are happy to let those be solved outside
> the core project.

I expect that one of the effects of having an "improved PITR" as a
'core' replication solution will be that Slony-I will become less
popular amongst "naive users," and that is *not* a bad thing.  I am
quite sure that there are a lot of cases today where users would be
better served by what falls out of this.

It will mean that those that are left will, despite being fewer, be
more cognizant that they are getting what they require.  

We should see somewhat fewer "expectation gaps," and that should allow
more people to be more satisfied with what they are getting.  
-- 
let name="cbbrowne" and tld="cbbrowne.com" in name ^ "@" ^ tld;;
http://linuxdatabases.info/info/linux.html
Lisp stoppped itself
FEP Command:


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_regress: referencing shared objects from tests
Next
From: Tom Lane
Date:
Subject: Re: Core team statement on replication in PostgreSQL