| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Path expansion in initdb |
| Date: | 2004-11-02 00:34:52 |
| Message-ID: | 200411020134.52513.peter_e@gmx.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-11-02 03:18:22 | Re: gettext calls in pgport |
| Previous Message | Gaetano Mendola | 2004-11-02 00:09:08 | Re: UPDATE is not allowed in a non-volatile function |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James William Pye | 2004-11-02 04:08:42 | Re: transformExpr() refactor |
| Previous Message | Guillaume LELARGE | 2004-11-01 23:33:52 | French translation updates for 8.0 |