Re: hot_standby_feedback parameter doesn't work - Mailing list pgsql-admin

From Andrey Zhidenkov
Subject Re: hot_standby_feedback parameter doesn't work
Date
Msg-id CAJw4d1UgWxd8S+Xog=dV8YV=S2wruTpro0n==ZHs6B5Cfx+iSQ@mail.gmail.com
Whole thread Raw
In response to Re: hot_standby_feedback parameter doesn't work  (Rui DeSousa <rui@crazybean.net>)
Responses Re: hot_standby_feedback parameter doesn't work  (Rui DeSousa <rui@crazybean.net>)
List pgsql-admin
On Tue, Nov 13, 2018 at 2:34 PM Rui DeSousa <rui@crazybean.net> wrote:
>
>
>
> > On Nov 12, 2018, at 10:28 PM, Andrey Zhidenkov <andrey.zhidenkov@gmail.com> wrote:
> >
> > We have a few database clusters (1 master, 2 hot standbys) with
> > hot_standby_feedback setting on. But I am constantly seeing query
> > conflicts on standbys because dead rows on the masters are deleted by
> > VACUUM. Usually I notice it shortly after VACUUM ends, because the
> > replication lag on replicas is starting to increase.
> >
> > vacuum_defer_cleanup_age = 0. PostgreSQL version is 9.5.13. Cluster
> > load is about 1500 transactions per second.
> >
> > Any ideas?
> >
> > -
> > With the best regards, Andrey Zhidenkov
> >
>
> Are these streaming replicas?  The wal_streaming process on the master should show the xmin of the replicas; you can
checkthe value from pg_stat_activity to make sure the feedback is occurring.
 
>
Yes, they are streaming replicas. Could you please tell me how to
check xmin of the replica in pg_stat_activity? I didn't get the point.

> Are the replicas disconnecting from the replication stream? As the would mean the xmin from the replica would no
longerbe in play.
 

No, the replicas are not disconnecting.

-- 
-
With best regards, Andrey Zhidenkov


pgsql-admin by date:

Previous
From: Achilleas Mantzios
Date:
Subject: Re: PostgreSQL 10.5 : Logical replication timeout results in PANIC inpg_wal "No space left on device"
Next
From: Andrew Gierth
Date:
Subject: Re: hot_standby_feedback parameter doesn't work