Re: BUG #16081: pg_upgrade is failed if a fake cmd.exe exist in the current directory.
> On 26 Oct 2019, at 06:32, PG Bug reporting form <[hidden email]> wrote:
> The following bug has been logged on the website:
> Bug reference: 16081
> Logged by: cili
> Email address: [hidden email] > PostgreSQL version: 12.0
> Operating system: Microsoft Windows [Version 10.0.18362.418]
> Similar to the case of pg_ctl. If a fake cmd.exe exits in current directory,
> pg_upgrade is failed to start.
> # 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”
pg_upgrade aborting an upgrade in a broken environment seems like proper
behavior. Not knowing Windows I might be missing something, but when is this
ever a legitimate usecase?