pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christopher Browne <cbbrowne@acm.org>
To: pgsql-admin@postgresql.org
Subject: Re: postgresql-R
Date: Wed, 08 Mar 2006 21:40:14 -0500
Message-ID: <877j74mjch.fsf@wolfe.cbbrowne.com> (raw)
References: <440DED31.1060704@linuxlouis.net>
	<20060307203530.GG58405@pervasive.com>
	<440DF3FF.9060001@linuxlouis.net>
	<D182E475-FCBC-4ADC-80EC-E70EDA3DF106@pervasive.com>
	<440F53A5.1080701@linuxlouis.net>

Clinging to sanity, louis.gonzales@linuxlouis.net (Louis Gonzales) mumbled into her beard:
> Hey Jim, Thanks again for the pointer to this.  I've already
> compiled and installed on one of the two Solaris nodes, that I
> needed to.  Yeah upon further reading, I can't wait for Slony-II to
> come out - is there truth behind the "anyday" rumor? - is it also
> true that it's going to implement the true multi-master scenario,
> where updates can be made at any of the clustered nodes.

I'm not holding my breath, at this point.

Performance results have indicated the Slony-II approach wouldn't work
out well for systems where there is heavy competition for locks on
some objects.  The trouble is that you wind up having to distribute
locks, and if the application has common heavily-updated objects, the
cost winds up prohibitive...

> I'm going to deploy the "slon worker process" locally on every
> participating node, rather than letting the master host the "slon"
> processes for every cluster participant, for performance reasons.

I run quite a lot of Slony-I nodes, and let me be pointed...
Performance is NOT a good reason (or a reason at all) to spread slon
processes across a bunch of hosts.

Performance of replication is based on the I/O taking place in the
databases; the costs of distributing some of the slon network traffic
will be fairly immaterial.

The "savings" from hosting slons on specific DB nodes is an illusion.
The data will all have to cross the network to get from sources to
providers, so whether the slon is on one host or another, you'll have
the same traffic transmitted around.

Having slons centralized makes it way simpler to manage them; I can't
see there being anywhere near enough benefit from any savings of
network traffic to actually represent a material performance
improvement.
-- 
wm(X,Y):-write(X),write('@'),write(Y). wm('cbbrowne','cbbrowne.com').
http://linuxdatabases.info/info/slony.html
Never criticize anybody until  you have walked  a mile in their shoes,
because by that time you will be a mile away and have their shoes.
-- email sig, Brian Servis



view thread (9+ messages)

Message-ID: <877j74mjch.fsf@wolfe.cbbrowne.com>
Permalink:  ../877j74mjch.fsf@wolfe.cbbrowne.com/
Also on:    postgresql.org/message-id/877j74mjch.fsf@wolfe.cbbrowne.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: cbbrowne@acm.org
  Subject: Re: postgresql-R
  In-Reply-To: <877j74mjch.fsf@wolfe.cbbrowne.com>
  References: <440DED31.1060704@linuxlouis.net> <20060307203530.GG58405@pervasive.com> <440DF3FF.9060001@linuxlouis.net> <D182E475-FCBC-4ADC-80EC-E70EDA3DF106@pervasive.com> <440F53A5.1080701@linuxlouis.net> <877j74mjch.fsf@wolfe.cbbrowne.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox