Re: pg_upgrade test failure
От | Andres Freund |
---|---|
Тема | Re: pg_upgrade test failure |
Дата | |
Msg-id | 20221018162908.cb3n7tahtekypbkf@awork3.anarazel.de обсуждение исходный текст |
Ответ на | Re: pg_upgrade test failure (Justin Pryzby <pryzby@telsasoft.com>) |
Ответы |
Re: pg_upgrade test failure
|
Список | pgsql-hackers |
Hi, On 2022-10-17 23:31:44 -0500, Justin Pryzby wrote: > On Tue, Oct 18, 2022 at 01:06:15PM +0900, Michael Paquier wrote: > > On Tue, Oct 18, 2022 at 09:47:37AM +1300, Thomas Munro wrote: > > > * Server 2019, as used on CI, still uses the traditional NT semantics > > > (unlink is asynchronous, when all handles closes) > > > * the fix I proposed has the right effect (I will follow up with tests > > > to demonstrate) > > > > Wow, nice investigation. And cirrus does not offer a newer option > > either.. > > Currently Andres builds images based on cirrus's 2019 image, but I think > we could use any windows docker image. You unfortunately can't run newer containers than the host OS :(, just user older ones. And if you use mismatching containers the startup gets slower because it switches to use full virtualization rather than containers. I think we need to switch to use full VMs rather than containers. The performance of the windows containers is just atrocious (build times on a local VM with the same number of cores is 1/2 of what we see in CI, test times 1/3), they're slow to start due to pulling all files and decompressing them, and they're fragile. I've asked Bilal (CCed) to work on generating both containers and images. Greetings, Andres Freund
В списке pgsql-hackers по дате отправления: