Re: Intermittent buildfarm failures on wrasse
От | Peter Geoghegan |
---|---|
Тема | Re: Intermittent buildfarm failures on wrasse |
Дата | |
Msg-id | CAH2-Wzn2Obp90oyZa5HN26rzG8ozzHM3dgkpLcsVzxTR+jK5NQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Intermittent buildfarm failures on wrasse (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Intermittent buildfarm failures on wrasse
|
Список | pgsql-hackers |
On Wed, Apr 13, 2022 at 4:51 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: > Yeah, we have band-aided around this type of problem repeatedly. > Making a fix that's readily accessible from any test script > seems like a good idea. We might even be able to consistently rely on this new option, given *any* problem involving test stability and VACUUM. Having a one-size-fits-all solution to these kinds of stability problems would be nice -- no more DISABLE_PAGE_SKIPPING bandaids. That general approach will be possible provided an inability to acquire a cleanup lock during VACUUM (which can more or less occur at random in most environments) doesn't ever lead to unexpected test results. There is good reason to think that it might work out that way. Simulating problems with acquiring cleanup locks during VACUUM left me with the impression that that could really work: https://postgr.es/m/CAH2-WzkiB-qcsBmWrpzP0nxvrQExoUts1d7TYShg_DrkOHeg4Q@mail.gmail.com -- Peter Geoghegan
В списке pgsql-hackers по дате отправления: