Re: pg_upgrade test failure
| От | Andres Freund |
|---|---|
| Тема | Re: pg_upgrade test failure |
| Дата | |
| Msg-id | 20220920011317.24bbsihqwn5dg7fi@awork3.anarazel.de обсуждение исходный текст |
| Ответ на | Re: pg_upgrade test failure (Michael Paquier <michael@paquier.xyz>) |
| Ответы |
Re: pg_upgrade test failure
|
| Список | pgsql-hackers |
Hi, On 2022-09-20 10:08:41 +0900, Michael Paquier wrote: > On Mon, Sep 19, 2022 at 02:32:17PM -0700, Andres Freund wrote: > > I don't know if actually related to the commit below, but there've been a > > lot of runs of the pg_upgrade tests in the meson branch, and this is the first > > failure of this kind. Unfortunately the error seems to be transient - > > rerunning the tests succeeded. > > This smells to me like a race condition in pg_upgrade (or even pg_ctl > for SERVER_LOG_FILE) where the code still has handles on some of the > files in the log/ subdirectory, causing its removal to not be able to > finish happen. I don't really see what'd race with what here? pg_upgrade has precise control over what's happening here, no? > If this proves to be rather easy to reproduce, giving > a list of the files still present in this path would give a hint easy > to follow. Does this reproduce with a good frequency? I've only seen it once so far, but there haven't been many CI runs of the meson branch since rebasing ontop of the last changes to pg_upgrade. Greetings, Andres Freund
В списке pgsql-hackers по дате отправления: