On Thu, Oct 14, 2010 at 8:58 PM, Aleksey Tsalolikhin
<atsaloli.tech at gmail.com> wrote:
> Dear Vick:  I do understand running slony replication will have SOME overhead.
> I just want to understand difference between 1.2 and 2.  If there is a
> big difference,
> it's a clear argument to move to 2.  Looks like I should do some
> testing in our test lab.

They both use the same basic technique of keeping a log table of
changes.  The big overhead comes from writing that log and running the
slony triggers.  Slony1 2.0 doesn't eliminate that overhead.

> And Vick, you asked:
>
> On Thu, Oct 7, 2010 at 1:01 PM, Vick Khera <vivek at khera.org> wrote:
>> How many rows are affected per update?  Slony replicates each row
>> specifically, not the queries themselves.  So if you update 10000
>> rows, there will be 10000 records for slony to copy over to the other
>> end.
>
> I have no idea.  I didn't write the queries, but I am (by default) the
> DBA.  How
> could I tell how many rows are affected per update?  (Feel free to RTFM me
> in the write direction.)
>

You inspect your queries.  Asking your developers may help.