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

****************************************************************
IMPORTANT: This message contains confidential information and is
intended only for the individual named. If the reader of this
message is not an intended recipient (or the individual
responsible for the delivery of this message to an intended
recipient), please be advised that any re-use, dissemination,
distribution or copying of this message is prohibited. Please
notify the sender immediately by e-mail if you have received
this e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or
error-free as information could be intercepted, corrupted, lost,
destroyed, arrive late or incomplete, or contain viruses. The
sender therefore does not accept liability for any errors or
omissions in the contents of this message, which arise as a
result of e-mail transmission.
****************************************************************