Re: Intermittent buildfarm failures on wrasse
От | Peter Geoghegan |
---|---|
Тема | Re: Intermittent buildfarm failures on wrasse |
Дата | |
Msg-id | CAH2-WzmOJ5YeT1SsBZ7kp2B+EMMVH9RYShornT13oyduEVwKSw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Intermittent buildfarm failures on wrasse (Andres Freund <andres@anarazel.de>) |
Ответы |
Re: Intermittent buildfarm failures on wrasse
|
Список | pgsql-hackers |
On Wed, Apr 13, 2022 at 4:13 PM Andres Freund <andres@anarazel.de> wrote: > IIRC the problem in matter isn't skipped pages, but that the horizon simply isn't new enough to mark pages as all visible. Sometimes OldestXmin can go backwards in VACUUM operations that are run in close succession against the same table, due to activity from other databases in the same cluster (perhaps other factors are involved at times). That's why the following assertion that I recently added to vacuumlazy.c will fail pretty quickly without the "vacrel->NewRelfrozenXid == OldestXmin" part of its test: Assert(vacrel->NewRelfrozenXid == OldestXmin || TransactionIdPrecedesOrEquals(aggressive ? FreezeLimit : vacrel->relfrozenxid, vacrel->NewRelfrozenXid)); If you remove "vacrel->NewRelfrozenXid == OldestXmin", and run the regression tests, the remaining assertion will fail quite easily. Though perhaps not with a serial "make check". -- Peter Geoghegan
В списке pgsql-hackers по дате отправления: