| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| 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 05:07:27 |
| Message-ID: | 20181113050727.vpx5kg3e5izxdn4l@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hi,
On 2018-11-13 10:28:20 +0700, Andrey Zhidenkov 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.
What's the precise conflict you get? I'd assume it's because of
exclusive locks, not row version conflicts. Is that right?
If so, that'd likely be because vacuum gets a chance to truncate the
relations at the end of vacuum.
Before theorizing further, it'd be good to get confirmation that that's
the right theory.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Zhidenkov | 2018-11-13 07:03:36 | Re: hot_standby_feedback parameter doesn't work |
| Previous Message | Rui DeSousa | 2018-11-13 04:47:53 | Re: hot_standby_feedback parameter doesn't work |