> You're arguments are very interesting.  When will you be releasing
your
code improvements?

Bill's comment is fair - my note was not constructive.  My apologies.

I should have added:

1. Is there any plan to enhance Slony to become a clustering solution?

2. If not, are there any other "official" open source projects for
clustering solution to postgres?  If not, would anyone be interested in
starting one with me?

-- Glen

-----Original Message-----
From: slony1-general-request at lists.slony.info
[mailto:slony1-general-request at lists.slony.info] 
Sent: Wednesday, 21 May 2008 5:00 AM
To: slony1-general at lists.slony.info
Subject: Slony1-general Digest, Vol 15, Issue 19

Send Slony1-general mailing list submissions to
	slony1-general at lists.slony.info

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.slony.info/mailman/listinfo/slony1-general
or, via email, send a message with subject or body 'help' to
	slony1-general-request at lists.slony.info

You can reach the person managing the list at
	slony1-general-owner at lists.slony.info

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Slony1-general digest..."


Today's Topics:

   1. True cluster (Glen Edmonds)
   2. Re: True cluster (Bill Moran)


----------------------------------------------------------------------

Message: 1
Date: Tue, 20 May 2008 14:09:28 +1000
From: "Glen Edmonds" <Glen.Edmonds at tafmo.com>
Subject: [Slony1-general] True cluster
To: <slony1-general at lists.slony.info>
Message-ID: <634262AC6200FF4598AEF683D6CDFEC51D280B at seth.tafmo.net>
Content-Type: text/plain; charset="us-ascii"

Hi,


If this is not an appropriate forum for these comments, please let me
know the best place to propose enhancements to functionality.

 

Here's my basic problem with slony and why I think it is not yet
"industrial strength":

 

Despite what the home page says, Slony is absolutely not a clustering
solution.  It is a replication solution.  For any database to have true
high availability (achievable 24/7 up time), it must have a clustering
solution.  Put simply, a cluster has these things:

 

1.	A cluster is comprised of any number of servers that behaves
like a single server and that is addressable by a single consistent
address
2.	A server may be added to the cluster at any time without any
downtime.  When a server is added, it brings itself up to date
automatically
3.	A server may be removed from the cluster at any time without any
downtime
4.	The failure of a server is detected by the cluster and it is
automatically excluded from the cluster without any downtime

 

Basically, you can add and remove servers whenever you like, and because
there's no single point of failure, it can stay up 24/7.
 

Slony can not do any of these things.  That's why I don't use postgres
for the transaction system - we have a 24/7 operation and we can't
guarantee achieving our SLAs with postgres.

 

Regards,

Glen

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.slony.info/pipermail/slony1-general/attachments/20080520/49
d0bda2/attachment.html

------------------------------

Message: 2
Date: Tue, 20 May 2008 08:29:00 -0400
From: Bill Moran <wmoran at collaborativefusion.com>
Subject: Re: [Slony1-general] True cluster
To: "Glen Edmonds" <Glen.Edmonds at tafmo.com>
Cc: slony1-general at lists.slony.info
Message-ID: <20080520082900.44ef044c.wmoran at collaborativefusion.com>
Content-Type: text/plain; charset=US-ASCII


You're arguments are very interesting.  When will you be releasing your
code improvements?

In response to "Glen Edmonds" <Glen.Edmonds at tafmo.com>:
> 
> If this is not an appropriate forum for these comments, please let me
> know the best place to propose enhancements to functionality.
> 
> Here's my basic problem with slony and why I think it is not yet
> "industrial strength":
> 
>  
> 
> Despite what the home page says, Slony is absolutely not a clustering
> solution.  It is a replication solution.  For any database to have
true
> high availability (achievable 24/7 up time), it must have a clustering
> solution.  Put simply, a cluster has these things:
> 
>  
> 
> 1.	A cluster is comprised of any number of servers that behaves
> like a single server and that is addressable by a single consistent
> address
> 2.	A server may be added to the cluster at any time without any
> downtime.  When a server is added, it brings itself up to date
> automatically
> 3.	A server may be removed from the cluster at any time without any
> downtime
> 4.	The failure of a server is detected by the cluster and it is
> automatically excluded from the cluster without any downtime
> 
>  
> 
> Basically, you can add and remove servers whenever you like, and
because
> there's no single point of failure, it can stay up 24/7.
> 
>  
> 
> Slony can not do any of these things.  That's why I don't use postgres
> for the transaction system - we have a 24/7 operation and we can't
> guarantee achieving our SLAs with postgres.
> 
>  
> 
> Regards,
> 
> Glen
> 
>  


-- 

Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/

wmoran at collaborativefusion.com
Phone: 412-422-3463x4023


------------------------------

_______________________________________________
Slony1-general mailing list
Slony1-general at lists.slony.info
http://lists.slony.info/mailman/listinfo/slony1-general


End of Slony1-general Digest, Vol 15, Issue 19
**********************************************