Collected from the PG bugs email list.
|OS||Microsoft Windows [Version 10.0.18362.418]|
Body of first available message related to this bug follows.
The following bug has been logged on the website: Bug reference: 16081 Logged by: cili Email address: (redacted) PostgreSQL version: 12.0 Operating system: Microsoft Windows [Version 10.0.18362.418] Description: Similar to the case of pg_ctl. If a fake cmd.exe exits in current directory, pg_upgrade is failed to start. Instructions: # cd %TEMP% # "c:\Program Files\PostgreSQL\12\bin\pg_ctl.exe" initdb -D test # set PGDATAOLD=%TEMP%\test # set PGDATANEW=%TEMP%\test # set PGBINOLD=c:\Program Files\PostgreSQL\12\bin # set PGBINNEW=c:\Program Files\PostgreSQL\12\bin # copy %windir%\system32\calc.exe cmd.exe # "c:\Program Files\PostgreSQL\12\bin\pg_upgrade" Performing Consistency Checks ----------------------------- Checking cluster versions ok *failure* Consult the last few lines of "pg_upgrade_server_start.log" or "pg_upgrade_server.log" for the probable cause of the failure. Expected: The database is upgraded. Actual: The Windows calculator is started and the upgrade command is failed.
|2019-10-26 04:32:55+00||PG Bug reporting form||BUG #16081: pg_upgrade is failed if a fake cmd.exe exist in the current directory.|
|2019-11-01 22:26:08+00||Daniel Gustafsson||Re: BUG #16081: pg_upgrade is failed if a fake cmd.exe exist in the current directory.|