Re: Race condition in recovery?
От | Dilip Kumar |
---|---|
Тема | Re: Race condition in recovery? |
Дата | |
Msg-id | CAFiTN-srU8=ND8z2wV8G+vhYZ4dMeWWNrFd0Cq0X9mDaL2ntAw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Race condition in recovery? (Kyotaro Horiguchi <horikyota.ntt@gmail.com>) |
Ответы |
Re: Race condition in recovery?
|
Список | pgsql-hackers |
On Fri, Jun 11, 2021 at 11:45 AM Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote: > > At Thu, 10 Jun 2021 21:53:18 -0400, Tom Lane <tgl@sss.pgh.pa.us> wrote in > tgl> Please note that conchuela and jacana are still failing ... > > I forgot jacana's case.. > > It is failing for the issue the first patch should have fixed. > > > ==~_~===-=-===~_~== pgsql.build/src/test/recovery/tmp_check/log/025_stuck_on_old_timeline_primary.log ==~_~===-=-===~_~== > ... > > The system cannot find the path specified. > > 2021-06-10 22:56:17.754 EDT [60c2d0cf.54c:1] LOG: archive command failed with exit code 1 > > 2021-06-10 22:56:17.754 EDT [60c2d0cf.54c:2] DETAIL: The failed archive command was: /usr/bin/perl "/home/pgrunner/bf/root/HEAD/pgsql/src/test/recovery/t/cp_history_files""pg_wal\\000000010000000000000001" "/home/pgrunner/bf/root/HEAD/pgsql.build/src/test/recovery/tmp_check/t_025_stuck_on_old_timeline_primary_data/archives/000000010000000000000001" Wal file copying will not create a problem for us, but I noticed that it is failing in copying the history files as well and that is creating a problem. 2021-06-10 22:56:28.940 EDT [60c2d0db.1208:1] LOG: archive command failed with exit code 1 2021-06-10 22:56:28.940 EDT [60c2d0db.1208:2] DETAIL: The failed archive command was: /usr/bin/perl "/home/pgrunner/bf/root/HEAD/pgsql/src/test/recovery/t/cp_history_files" "pg_wal\\00000002.history" "/home/pgrunner/bf/root/HEAD/pgsql.build/src/test/recovery/tmp_check/t_025_stuck_on_old_timeline_primary_data/archives/00000002.history" I have noticed that the archive command is failing in some other test case too (002_archiving_standby2.log), see below logs. ==~_~===-=-===~_~== pgsql.build/src/test/recovery/tmp_check/log/002_archiving_standby2.log ==~_~===-=-===~_~== ... 0 file(s) copied. 2021-06-10 22:44:34.467 EDT [60c2ce10.1270:1] LOG: archive command failed with exit code 1 2021-06-10 22:44:34.467 EDT [60c2ce10.1270:2] DETAIL: The failed archive command was: copy "pg_wal\\00000003.history" "c:/mingw/msys/1.0/home/pgrunner/bf/root/HEAD/pgsql.build/src/test/recovery/tmp_check/t_002_archiving_primary_data/archives\\00000003.history" The system cannot find the path specified. 0 file(s) copied. 2021-06-10 22:44:35.478 EDT [60c2ce10.1270:3] LOG: archive command failed with exit code 1 2021-06-10 22:44:35.478 EDT [60c2ce10.1270:4] DETAIL: The failed archive command was: copy "pg_wal\\00000003.history" "c:/mingw/msys/1.0/home/pgrunner/bf/root/HEAD/pgsql.build/src/test/recovery/tmp_check/t_002_archiving_primary_data/archives\\00000003.history" 2021-06-10 22:44:36.113 EDT [60c2ce0c.283c:5] LOG: received immediate shutdown request 2021-06-10 22:44:36.129 EDT [60c2ce0c.283c:6] LOG: database system is shut down I am not able to figure out why the archive command is failing. -- Regards, Dilip Kumar EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: