On Fri, Nov 9, 2018 at 2:25 AM Thomas Munro <thomas.munro@enterprisedb.com> wrote:We saw a variant of this problem on appveyor (a Windows build-bot) when testing Daniel's patch to add an optional message (search for "timing"), and it was fixed as part of that patch, for the new code in that patch:https://www.postgresql.org/message-id/flat/C2C7C3EC-CC5F-44B6-9C78-637C88BD7D14@yesql.se Perhaps other pre-existing tests need similar treatment?Ah yes, that seems to be the same thing, and yes that seem like a reasonalbe solution. So something like:+select case+ when pg_cancel_backend(pg_backend_pid())+ then pg_sleep(60)+end; Alexander, can you check to see if making that change solves the issue on your machine?
We saw a variant of this problem on appveyor (a Windows build-bot) when testing Daniel's patch to add an optional message (search for "timing"), and it was fixed as part of that patch, for the new code in that patch:https://www.postgresql.org/message-id/flat/C2C7C3EC-CC5F-44B6-9C78-637C88BD7D14@yesql.se Perhaps other pre-existing tests need similar treatment?
pgsql-bugs by date:
Соглашаюсь с условиями обработки персональных данных