Re: [PATCH] Bug fix in initdb output

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com>
Cc: Nitin Jadhav <nitinjadhavpostgres(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Bug fix in initdb output
Date: 2021-03-01 18:16:08
Message-ID: 20210301181608.GA25758@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2021-Mar-01, Juan José Santamaría Flecha wrote:

> On Mon, Mar 1, 2021 at 5:52 AM Nitin Jadhav <nitinjadhavpostgres(at)gmail(dot)com>
> wrote:
>
> >
> >> Please share your thoughts on this. If we go ahead with this change,
> > then we need to back-patch. I would be happy to create those patches.
>
> A full path works, even with the slashes. The commiter will take care of
> back-patching, if needed. As for HEAD at least, this LGTM.

I don't get it. I thought the windows API accepted both forward slashes
and backslashes as path separators. Did you try the command and see it
fail?

--
Álvaro Herrera 39°49'30"S 73°17'W
"Entristecido, Wutra (canción de Las Barreras)
echa a Freyr a rodar
y a nosotros al mar"

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Dilger 2021-03-01 18:22:35 Re: [PATCH] Cross-reference comments on signal handling logic
Previous Message Mark Dilger 2021-03-01 18:12:54 Re: Add --tablespace option to reindexdb