Long running activity or idle in transactions are not there on either master or slave as we stop all connections to both the DBs during vacuum.
Regards,
Granthana
On Fri, Mar 21, 2014 at 8:51 PM, Sergey Konoplev <gray.ru@gmail.com> wrote:
On Fri, Mar 21, 2014 at 2:46 AM, Granthana Biswas <granthana@zedo.com> wrote: > We don't have two-phase commit prepared transactions. During vacuum, along with this problem we are also facing streaming replication issue. Hundreds of xlogs are in ready state in pg_xlog/archive_status. Those are being copied manually after vacuum otherwise rsync happens very slowly and replication lag keeps increasing.
Okay, I see. Then next questions are:
What postgres version is it? What max_standby_archive_delay and max_standby_streaming_delay are set to? Are there any long running activity or idling in transaction backends on your slaves?
-- Kind regards, Sergey Konoplev PostgreSQL Consultant and DBA
