Horton

Re: [PATCH] Bug fix in initdb output

Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>

View thread View on postgr.es
From: Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, Nitin Jadhav <nitinjadhavpostgres@gmail.com>, Michael Paquier <michael@paquier.xyz>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2021-03-22T08:36:46Z
Lists: pgsql-hackers 
On Sun, Mar 21, 2021 at 10:28 PM Andrew Dunstan <andrew@dunslane.net> wrote:

>
> Note that the pg_ctl path is quoted, and those quotes are passed through
> to cmd.exe. That's what makes it work. It's possibly not worth changing
> it now, but if anything that's the change that should have been made here.
>
> The OP claimed that the printed command was not working 'as-is', which is
a valid complaint.

Quoting the command seems like a complete answer for this, as it will solve
problems with spaces and such for both Windows and Unix-like systems.

Regards,

Juan José Santamaría Flecha

Commits

  1. Use native path separators to pg_ctl in initdb

  2. Have initdb display relative paths to start postmaster if used to invoke