Re: [PATCH] Bug fix in initdb output
Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>
From: Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Nitin Jadhav <nitinjadhavpostgres@gmail.com>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2021-03-01T18:57:51Z
Lists: pgsql-hackers
On Mon, Mar 1, 2021 at 7:50 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: > On 2021-Mar-01, Juan José Santamaría Flecha wrote: > > > This is not a problem with the APi, but the shell. e.g. when using a CMD: > > > > - This works: > > c:\>c:\Windows\System32\notepad.exe > > c:\>c:/Windows/System32/notepad.exe > > c:\>/Windows/System32/notepad.exe > > > > - This doesn't: > > c:\>./Windows/System32/notepad.exe > > '.' is not recognized as an internal or external command, > > operable program or batch file. > > c:\>Windows/System32/notepad.exe > > 'Windows' is not recognized as an internal or external command, > > operable program or batch file. > > Ah, so another way to fix it would be to make the path to pg_ctl be > absolute? > Yes, that's right. If you call initdb with an absolute path you won't see a problem. Regards, Juan José Santamaría Flecha
Commits
-
Use native path separators to pg_ctl in initdb
- f927767919e8 12.7 landed
- b52fd1e7c76c 13.3 landed
- ae1c1d84ea24 11.12 landed
- 926139dd04bb 10.17 landed
- 75dbfe4ca70d 14.0 landed
-
Have initdb display relative paths to start postmaster if used to invoke
- ee814b4511ec 8.0.0 cited