| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 00:35:02 |
| Message-ID: | 20220414003502.fmcm3wcgjw5zk5ax@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2022-04-13 16:45:44 -0700, Peter Geoghegan wrote:
> On Wed, Apr 13, 2022 at 4:38 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > So what seems to be happening on wrasse is that a background
> > autovacuum (or really autoanalyze?) is preventing pages from
> > being marked all-visible not only during test_setup.sql but
> > also create_index.sql; but it's gone by the time sanity_check.sql
> > runs.
>
> I agree that it would need to be an autoanalyze (due to the
> PROC_IN_VACUUM optimization).
That's not a realiable protection - the snapshot is established normally
at first, only after a while we set PROC_IN_VACUUM...
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-04-14 00:35:50 | Re: Intermittent buildfarm failures on wrasse |
| Previous Message | Justin Pryzby | 2022-04-14 00:33:01 | Re: typos |