Dear Thomas, Alexander, > 17.12.2023 07:02, Thomas Munro wrote: > > FYI fairywren failed in this test: > > > > > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=fairywren&dt=2023-1 > 2-16%2022%3A03%3A06 > > > > ===8<=== > > Restoring database schemas in the new cluster > > *failure* > > > > Consult the last few lines of > > > "C:/tools/nmsys64/home/pgrunner/bf/root/HEAD/pgsql.build/testrun/pg_upgr > ade/003_logical_slots/data/t_003_logical_slots_newpub_data/pgdata/pg_upgra > de_output.d/20231216T221418.035/log/pg_upgrade_dump_1.log" > > for > > the probable cause of the failure. > > Failure, exiting > > [22:14:34.598](22.801s) not ok 10 - run of pg_upgrade of old cluster > > [22:14:34.600](0.001s) # Failed test 'run of pg_upgrade of old cluster' > > # at > C:/tools/nmsys64/home/pgrunner/bf/root/HEAD/pgsql/src/bin/pg_upgrade/t/ > 003_logical_slots.pl > > line 177. > > ===8<=== > > > > Without that log it might be hard to figure out what went wrong though :-/ > > > > Yes, but most probably it's the same failure as >
Thanks for reporting. Yes, it has been already reported by me [1], and the server log was provided by Andrew [2]. The issue was that a file creation was failed because the same one was unlink()'d just before but it was in STATUS_DELETE_PENDING status. Kindly Alexander proposed a fix [3] and it looks good to me, but confirmations by senior and windows-friendly developers are needed to move forward. (at first we thought the issue was solved by updating, but it was not correct) I know that you have developed there region, so I'm very happy if you check the forked thread. [1]: https://www.postgresql.org/message-id/flat/TYAPR01MB5866AB7FD922CE30A2565B8BF5A8A%40TYAPR01MB5866.jpnprd01.prod.outlook.com [2]: https://www.postgresql.org/message-id/TYAPR01MB5866A4E7342088E91362BEF0F5BBA%40TYAPR01MB5866.jpnprd01.prod.outlook.com [3]: https://www.postgresql.org/message-id/976479cf-dd66-ca19-f40c-5640e30700cb%40gmail.com Best Regards, Hayato Kuroda FUJITSU LIMITED
