Re: Weird test mixup
| От | Michael Paquier |
|---|---|
| Тема | Re: Weird test mixup |
| Дата | |
| Msg-id | ZfOABU4ahF2QZQ6N@paquier.xyz обсуждение исходный текст |
| Ответ на | Re: Weird test mixup (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Weird test mixup
Re: Weird test mixup |
| Список | pgsql-hackers |
On Thu, Mar 14, 2024 at 06:19:38PM -0400, Tom Lane wrote: > Do they? It'd be fairly easy to explain this if these things were > being run in "installcheck" style. I'm not sure about CI, but from > memory, the buildfarm does use installcheck for some things. > > I wonder if it'd be wise to adjust the injection point stuff so that > it's active in only the specific database the injection point was > activated in. It can be made optional by extending InjectionPointAttach() to specify a database OID or a database name. Note that 041_checkpoint_at_promote.pl wants an injection point to run in the checkpointer, where we don't have a database requirement. Or we could just disable runningcheck because of the concurrency requirement in this test. The test would still be able to run, just less times. -- Michael
Вложения
В списке pgsql-hackers по дате отправления: