Re: [PATCH] Bug fix in initdb output - Mailing list pgsql-hackers

From Juan José Santamaría Flecha
Subject Re: [PATCH] Bug fix in initdb output
Date
Msg-id CAC+AXB282NnXjh4qVdMKbOyWaPd-eDG-fUrmigHi_1avPePVHA@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Bug fix in initdb output  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: [PATCH] Bug fix in initdb output  (Andrew Dunstan <andrew@dunslane.net>)
List 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
 

pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: problem with RETURNING and update row movement
Next
From: Peter Eisentraut
Date:
Subject: Re: [PATCH] Identify LWLocks in tracepoints