Aldor <an at mediaroot.de> writes:
> I was talking about tables which are NOT in the replication set.

And what are you doing with them?

Is it inserts that wind up slow?  

Or is it SELECTs?

Or is is it COPY?

In any case, if those tables aren't involved in replication, Slony-I
won't touch them.

There CAN be systematic effects from having replication around, in
terms of:
 a) Slony-I doing work to replicate data, which consumes resources;
 b) Replication work consuming cache, meaning unrelated processes
    won't get to use that cache.

But generally the negative side-effects go the other way around.
 - Long running transactions cause build-up of dead tuples in
   Slony-I specific tables;
 - This slows replication performance so that subscribers can
   fall behind.

It's usually that exogenous things adversely affect Slony-I, not that
it adversely affects things that are seemingly unrelated.
-- 
"cbbrowne","@","ca.afilias.info"
<http://dev6.int.libertyrms.com/>
Christopher Browne
(416) 673-4124 (land)