Re: [GENERAL] pg_stat_replication became empty suddenly

Thanks. I increased the wal_keep_segments and it works well now. On 7 Aug 2013, at 12:43 AM, Jerry Sievers wrote: > "ascot.m...@gmail.com" writes: > >> Hi, >> >> I just tried another round of tests, without running "sync; echo 3 > >> /proc/sys/vm/drop_caches', >> still got the same error,

Re: [GENERAL] pg_stat_replication became empty suddenly

"ascot.m...@gmail.com" writes: > Hi, > > I just tried another round of tests, without running "sync; echo 3 > > /proc/sys/vm/drop_caches', > still got the same error, following FATAL errors are found in pg_log > (slave), can anyone please advise how to resolve > this error? > > regards > > LO

Re: [GENERAL] pg_stat_replication became empty suddenly

Hi, I just tried another round of tests, without running "sync; echo 3 > /proc/sys/vm/drop_caches', still got the same error, following FATAL errors are found in pg_log (slave), can anyone please advise how to resolve this error? regards LOG: entering standby mode LOG: consistent recovery

Re: [GENERAL] pg_stat_replication became empty suddenly

Hi, I found the problem should be because I tried to clean RAM cache in the slave by running "sync; echo 3 > /proc/sys/vm/drop_caches' that caused the "receiver" of slave gone away. ps -ef | grep receiver postgres 6182 6178 0 12:11 ?00:00:06 postgres: wal receiver process