[Slony1-general] Too much data update...

[Sebastien Marchand]

Thanks for the answer, keep-alive can't help in this case i think. ( too 
many rows ( 11 millions ))

And as you say, 11 millions rows created in one transaction, that the 
problem. So i deleted all rows in sl_log_1 et 2, (only one table updated 
here)

I will copy just this table with compression or another technic, slony 
will see anything i think/hope.

For the future i will test the log shipping.

Thanks


Le 26/03/2020 à 12:54, Steve Singer a écrit :
> On Thu, 26 Mar 2020, Sebastien Marchand via Slony1-general wrote:
>
>> Hi,
>>
>> I've got a replication fully fonctionnal, but after a big update of 
>> datas, the master doesn't succeed to sent all datas ( 7gB ) because 
>> their line is too bad ( 60kB/s UP ).
>>
>> Can i set an option to sent less data in one time ?
>
>
> Normal replication needs to send all the data from a given database 
> transaction on the origin to a single transaction on the replica.  
> Maybe playing wtih the tcp keep-alive settings will help? 
> https://www.slony.info/documentation/2.2/slon-config-connection.html
>
> If not log shipping would let you send the data via files 
> https://www.slony.info/documentation/2.2/logshipping.html
>
>
> Steve
>
>>
>> thanks in advance
>>
>>
>> Sébastien Marchand.
>>
>> _______________________________________________
>> Slony1-general mailing list
>> Slony1-general at lists.slony.info
>> http://lists.slony.info/mailman/listinfo/slony1-general
>>