|
From: Paulo P. <pj...@ub...> - 2012-10-25 07:43:52
|
On 25/10/12 08:37, Vladimir Stavrinov wrote: > On Thu, Oct 25, 2012 at 2:05 AM, Vladimir Stavrinov > <vst...@gm...> wrote: >> On Wed, Oct 24, 2012 at 11:18:59PM +0300, Andrei Martsinchyk wrote: >>> one of those solutions. Everybody wins. If XC integrates one >>> approach it will lose flexibility in this area. >> and gain much more users. > OK. Paulo don't wants more users, because he don't like easy ways and > simple things. But we all want flexibility. Flexibility is good thing > and here is example. I didn't say "I don't want more users". I just believe, based on my experience, that subjects as advanced as the ones we're discussing don't come easy. And they shouldn't in the sense that people should really learn/know about what they're doing, regarding clustering, HA, etc.! > > We have cluster consists of 4 nodes. Nodes organized in groups. All > data distributed between groups and every group contains the identical > data, i.e. replicas. In this case with such model we have 3 options: > > 1. Read scalability only with 4 replicas in group. > 2. Read and write scalability with 2 replicas per group. > 3. Write scalability only with 1 replica per group. > > It is obvious: with more nodes we have more options, i.e. more > flexibility. It means here the trade off between read and write > scalability. And we don't need for this "CREATE TABLE ... DISTRIBUTE > BY ..." I think it is enough for most cases. > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > _______________________________________________ > Postgres-xc-general mailing list > Pos...@li... > https://lists.sourceforge.net/lists/listinfo/postgres-xc-general -- Paulo Pires |