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 20:09:29
Message-ID: 20210301200929.GA5763@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 7:50 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
> wrote:

> > 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.

So, is make_native_path a better fix than make_absolute_path? (I find
it pretty surprising that initdb shows a relative path, but maybe that's
just me.)

--
Álvaro Herrera 39°49'30"S 73°17'W
"How strange it is to find the words "Perl" and "saner" in such close
proximity, with no apparent sense of irony. I doubt that Larry himself
could have managed it." (ncm, http://lwn.net/Articles/174769/)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Dilger 2021-03-01 20:20:31 Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index.
Previous Message Andres Freund 2021-03-01 20:07:15 buildfarm windows checks / tap tests on windows