| From: | Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| 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:49:25 |
| Message-ID: | CAC+AXB1BgF_H_uEoGtQ125dhOjL0H8N2gpYdURz8BFGvXKKAtw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 1, 2021 at 9:09 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
wrote:
> 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.)
>
Uhm, now that you point it out, an absolute path would make the message
more consistent and reusable.
Regards,
Juan José Santamaría Flecha
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2021-03-01 20:49:35 | Re: Use extended statistics to estimate (Var op Var) clauses |
| Previous Message | Tomas Vondra | 2021-03-01 20:40:27 | Re: [PoC] Non-volatile WAL buffer |