Re: Intermittent buildfarm failures on wrasse
От | Andres Freund |
---|---|
Тема | Re: Intermittent buildfarm failures on wrasse |
Дата | |
Msg-id | 20220414015112.yhruzx3dbjnz4pji@alap3.anarazel.de обсуждение исходный текст |
Ответ на | Re: Intermittent buildfarm failures on wrasse (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Intermittent buildfarm failures on wrasse
Re: Intermittent buildfarm failures on wrasse |
Список | pgsql-hackers |
Hi, Noah, any chance you could enable log_autovacuum_min_duration=0 on wrasse? On 2022-04-13 21:23:12 -0400, Tom Lane wrote: > I'm still suspicious of the pgstat changes, though. I checked into > things here by doing > > initdb > edit postgresql.conf to set log_autovacuum_min_duration = 0 > pg_ctl start && make installcheck-parallel > > and what I see is that the first reported autovacuum activity begins > exactly one minute after the postmaster starts, which is what I'd > expect given the autovacuum naptime rules. It'd not necessarily have to be autovacuum. A CREATE INDEX or VACUUM using parallelism, could also cause this, I think. It'd be a narrow window, of course... Does sparc have wider alignment rules for some types? Perhaps that'd be enough to put some tables to be sufficiently larger to trigger parallel vacuum? Greetings, Andres Freund
В списке pgsql-hackers по дате отправления: