it was very stupid :) on master there was cron which was killing very long idle in transaction postgres processes, and every time when on slave huge table was analyzing (by finishTableAfterCopy) on master some process became idle in transaction ...
i haven't  thougt that could be problem generated by another machine, and on the slave wasn't any info in logs.

Sebastian Pawlowski

Wiadomość napisana przez Stéphane A. Schildknecht <stephane.schildknecht at postgresql.fr> w dniu 19 wrz 2012, o godz. 08:49:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Le 18/09/2012 17:59, Sebastian Paw?owski a écrit :
>> problem solved
>> 
> 
> Which was?
> 
> 
> - -- 
> Stéphane Schildknecht
> http://www.Loxodata.com
> Contact régional PostgreSQL
> http://bistri.me/sas
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
> 
> iEYEARECAAYFAlBZauEACgkQA+REPKWGI0FmrACfflkU1yY0Gln5kZQPWQPF5g0H
> FNsAmwUeSc2NSm/UCGBUiQ+YynHqpXo/
> =Psjz
> -----END PGP SIGNATURE-----
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general