Re: Intermittent pg_ctl failures on Windows
r.zharkov@postgrespro.ru
From: r.zharkov@postgrespro.ru
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Michael Paquier <michael@paquier.xyz>, Badrul Chowdhury
<bachow@microsoft.com>, pgsql-hackers@lists.postgresql.org
Date: 2019-07-19T08:35:42Z
Lists: pgsql-hackers
Attachments
- test.pl (text/plain)
- sharing_violation.PNG (image/png)
- process_tree.PNG (image/png)
- regress_log_test (text/plain)
Hello, I have reproduced the CMD.EXE error "The process cannot access the file because it is being used by another process" the REL_12_STABLE. I simply launched my dummy TAP test and I got «Процесс не может получить доступ к файлу, так как этот файл занят другим процессом.» ( “The process cannot access the file because it is being used by another process” in english Windows version ) The pictures in the attachment illustrate the SHARING_VIOLATION error. ------------------------------------------- # Postmaster PID for node "master" is 10456 # restarted 32 # 13:28:58 ### Restarting node "master" # Running: pg_ctl -D C:/HOME/Git/postgrespro/src/test/pg_ctl/tmp_check/t_test_master_data/pgdata -l C:/HOME/Git/postgrespro/src/test/pg_ctl/tmp_check/log/test_master.log restart waiting for server to shut down.... done server stopped waiting for server to start....Процесс не может получить доступ к файлу, так как этот файл занят другим процессом. stopped waiting pg_ctl: could not start server Examine the log output. Bail out! system pg_ctl failed ### Stopping node "master" using mode immediate # Running: pg_ctl -D C:/HOME/Git/postgrespro/src/test/pg_ctl/tmp_check/t_test_master_data/pgdata -m immediate stop pg_ctl: PID file "C:/HOME/Git/postgrespro/src/test/pg_ctl/tmp_check/t_test_master_data/pgdata/postmaster.pid" does not exist Is server running? Bail out! system pg_ctl failed ------------------------------------------ -- regards, Roman
Commits
-
Allow concurrent-safe open() and fopen() in frontend code for Windows
- f02259fe93e7 11.0 landed
- 0ba06e0bfb8c 12.0 landed
-
Change pg_ctl to detect server-ready by watching status in postmaster.pid.
- f13ea95f9e47 10.0 cited