What was the resolution of this? Can we make relative -L work or do we add error checks for relative -L paths?
--------------------------------------------------------------------------- Josh Berkus wrote: > 8.0 beta CVS of 8/8/2004: > > If a relative path is used for the -L option in initdb, the following fatal > error happens: > > ./initdb -D ../data -L ../share/postgresql/ > <snip> > creating system views ... ok > loading pg_description ... ERROR: could not open file > "../share/postgresql/postgres.description" for reading: No such file or > directory > child process exited with exit code 1 > > Is this intentional? The first dozen or so commands work fine with a relative > path, and this executes fine with an absolute path for both -D and -L. > > SuSE 9.1, GCC 3.3.3 > > -- > Josh Berkus > Aglio Database Solutions > San Francisco > > ---------------------------(end of broadcast)--------------------------- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED]) > -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
