| From: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Peter Geoghegan <pg(at)bowt(dot)ie>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Noah Misch <noah(at)leadboat(dot)com> |
| Subject: | Re: Vacuum ERRORs out considering freezing dead tuples from before OldestXmin |
| Date: | 2024-06-25 15:39:03 |
| Message-ID: | CAAKRu_aT6Go_=e9gvXf0gtVw3c9p_bq7WoCqKyFM2KKXJ_GtFg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 25, 2024 at 10:31 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> On Tue, Jun 25, 2024 at 9:07 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
> > It's not hard - but it has downsides. It'll mean that - outside of vacuum -
> > we'll much more often not react to horizons going backwards due to
> > hot_standby_feedback. Which means that hot_standby_feedback, when used without
> > slots, will prevent fewer conflicts.
>
> Can you explain this in more detail?
If we prevent GlobalVisState from moving backward, then we would less
frequently be pushing the horizon backward on the primary in response
to hot standby feedback. Then, the primary would do more things that
would not be safely replayable on the standby -- so the standby could
end up encountering more recovery conflicts.
- Melanie
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vignesh C | 2024-06-25 15:39:17 | Re: Logical Replication of sequences |
| Previous Message | Nathan Bossart | 2024-06-25 15:35:51 | Re: improve predefined roles documentation |