| From: | Rui DeSousa <rui(at)crazybean(dot)net> |
|---|---|
| To: | Andrey Zhidenkov <andrey(dot)zhidenkov(at)gmail(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: hot_standby_feedback parameter doesn't work |
| Date: | 2018-11-13 04:47:53 |
| Message-ID: | 06C4AE86-9E7F-40E6-B851-AE898CDFA965@crazybean.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> On Nov 12, 2018, at 10:28 PM, Andrey Zhidenkov <andrey(dot)zhidenkov(at)gmail(dot)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 check the value from pg_stat_activity to make sure the feedback is occurring.
Are the replicas disconnecting from the replication stream? As the would mean the xmin from the replica would no longer be in play.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-11-13 05:07:27 | Re: hot_standby_feedback parameter doesn't work |
| Previous Message | Nikhil Shetty | 2018-11-13 04:19:17 | Re: How to downgrade a cluster from 9.5 to 9.3 |