Path expansion in initdb

It used to be that calling

initdb -D /some/where

suggested starting

postmaster -D /some/where

and

./mydir/bin/initdb -D ./mydir/var/data

suggested starting

./mydir/bin/postmaster -D ./mydir/var/data

In the current sources, the path to the postmaster is fully expanded in
either case (resulting in something like
/home/peter/./mydir/bin/postmaster in the second case). (Curiously,
the data directory path is not changed.) I don't find this to be an
improvement. Is there a reason for this change?

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

Peter Eisentraut wrote:
> It used to be that calling
>
> initdb -D /some/where
>
> suggested starting
>
> postmaster -D /some/where
>
> and
>
> ./mydir/bin/initdb -D ./mydir/var/data
>
> suggested starting
>
> ./mydir/bin/postmaster -D ./mydir/var/data
>
> In the current sources, the path to the postmaster is fully expanded in
> either case (resulting in something like
> /home/peter/./mydir/bin/postmaster in the second case). (Curiously,
> the data directory path is not changed.) I don't find this to be an
> improvement. Is there a reason for this change?

I have applied the following patch to address your concerns. We needed
this anyway because we were not using native paths in the display.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073