Hi!

(back on the mailing list - I accedentially replied directly)

I have no more ideas. Sometimes we also have the problem of a slave not 
syncing any more. In our case, sometimes it helps to remove the slave 
from the cluster and add it again (of course the slave is then offline 
for some time - so this might not always be possible).

regards
Klaus

Am 31.07.2019 um 23:56 schrieb Rajni Baliyan:
> Thanks Klaus,
> We can rule out the possibility of Network and slow disk.
> For slow database, yes we are reindexing many replicated tables . Do I 
> need to reindex any sl_* tables as well?
> 
> Replication was running fine with 2mins delay and had this issue after 
> adding schema and table on master( did on slaves as well)
> 
> Is there a way I can see what exactly slony is currently doing? As logs 
> doesn't says anything.
> 
> There are many idle connection of slony and waiting is 'f' in 
> pg_stat_activity. Any idea why connections goes ideal when sync is in 
> progress.
> 
> Can I tune any parameter to make it faster.
> 
> Thanks in advance.
> Regards,
> Saan
> 
> On Thu, Aug 1, 2019 at 1:26 AM Klaus Darilion 
> <klaus.mailinglists at pernau.at <mailto:klaus.mailinglists at pernau.at>> wrote:
> 
> 
> 
>     Am 30.07.2019 um 09:39 schrieb Rajni Baliyan:
>      > Hello team ,
>      > I am running Slony 2.2.4 on PostgreSQL 9.2.8( please excuse for using
>      > unsupported version) and having slowness issues.
>      >
>      > Any help in this regard would be greatly appreciated.
> 
>     This can have multiple purposes:
>     - Bad network connectivity to slave (packet loss, slow ...)
>     - Slow disk-IO on slave
>     - Slow database on slave (for me it sometimes help to reindex to clean
>     up index bloat and let the index/DB fit into RAM again)
> 
>     regards
>     Klaus
>