pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #16081: pg_upgrade is failed if a fake cmd.exe exist in the current directory.
2+ messages / 2 participants
[nested] [flat]
* BUG #16081: pg_upgrade is failed if a fake cmd.exe exist in the current directory.
@ 2019-10-26 04:32 PG Bug reporting form <noreply@postgresql.org>
0 siblings, 1 reply; 2+ messages in thread
From: PG Bug reporting form @ 2019-10-26 04:32 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org; +Cc: cilizili@protonmail.com
The following bug has been logged on the website:
Bug reference: 16081
Logged by: cili
Email address: cilizili@protonmail.com
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.
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: BUG #16081: pg_upgrade is failed if a fake cmd.exe exist in the current directory.
@ 2019-11-01 22:26 Daniel Gustafsson <daniel@yesql.se>
parent: PG Bug reporting form <noreply@postgresql.org>
0 siblings, 0 replies; 2+ messages in thread
From: Daniel Gustafsson @ 2019-11-01 22:26 UTC (permalink / raw)
To: cilizili@protonmail.com, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
> On 26 Oct 2019, at 06:32, PG Bug reporting form <noreply@postgresql.org> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference: 16081
> Logged by: cili
> Email address: cilizili@protonmail.com
> 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ā
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?
cheers ./daniel
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2019-11-01 22:26 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2019-10-26 04:32 BUG #16081: pg_upgrade is failed if a fake cmd.exe exist in the current directory. PG Bug reporting form <noreply@postgresql.org>
2019-11-01 22:26 ` Daniel Gustafsson <daniel@yesql.se>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox