| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Intermittent buildfarm failures on wrasse |
| Date: | 2022-04-14 01:05:15 |
| Message-ID: | CAH2-Wz=v5DiwMcFkGHAq79TbArz7tKaGAOxoD3AxscZ1KB=2BA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 13, 2022 at 6:03 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> I think that it's more likely that FREEZE will correct problems, out of the two:
>
> * FREEZE forces an aggressive VACUUM whose FreezeLimit is as recent a
> cutoff value as possible (FreezeLimit will be equal to OldestXmin).
The reason why that might have helped (at least in the past) is that
it's enough to force us to wait for a cleanup lock to prune and
freeze, if necessary. Which was never something that
DISABLE_PAGE_SKIPPING could do.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2022-04-14 01:08:08 | Re: Intermittent buildfarm failures on wrasse |
| Previous Message | Andres Freund | 2022-04-14 01:05:05 | Re: Intermittent buildfarm failures on wrasse |