Hi Everydoby

I started using SLONY-I for a simple large DB replication. As my team collegues started to change the scope of the project, if I can call it project, I realized sometimes constraints in the SLONY usage.

That s why I wanted to know generally , based on the experience of everyone ; where did U found CONSTRAINTs or PROBLEMs (generally) while using SLONY in a project and not in a simple DB replication. As example for what I am looking for is :
- SLONY-I is "good" by handling random() values because I will not have different random-Vals in Master or Slave , what is not the case of PGCluster.
- A disadvantage, as example, can be that SLONY-I can not handle a project that needs every week or day a new database because, we can not stop a replication , but we must add a new set.
- Another example is that one may use lot of sets by a large number of DBs to avoid deadlocks, thing that makes the administration more complicated...

I mean according to your projects and your expereince, where did one of you all see some problems.


Thanks again
-----------------------------------------------------------------------------------------------------------------------------------
Christopher Browne wrote:
> Largo Stemper wrote:
>> Can someone help me by giving me a briefing listing the disadvantages of SLONY-I.
>>   
> Disadvantages (and advantages) do not exist in a vacuum.
>
> They have to be framed in some context; Slony-I can only have advantages
> or disadvantages when compared to something else.
>
> You can't conceivably have either sort of "vantage" without specifying
> that "something else."


_______________________________________________________________________
Viren-Scan f?r Ihren PC! Jetzt f?r jeden. Sofort, online und kostenlos.
Gleich testen! http://www.pc-sicherheit.web.de/freescan/?mc=022222