Path expansion in initdb

Started by Peter Eisentrautover 21 years ago2 messageshackers
Jump to latest
#1Peter Eisentraut
peter_e@gmx.net

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/

#2Bruce Momjian
bruce@momjian.us
In reply to: Peter Eisentraut (#1)
Re: [HACKERS] Path expansion in initdb

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@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

Attachments:

/bjm/difftext/plainDownload+19-10