Re: [HACKERS] Strange code in initdb

2004-10-15 Thread Bruce Momjian
Peter Eisentraut wrote: > Am Freitag, 15. Oktober 2004 06:24 schrieb Bruce Momjian: > > I have modified these reports so they print the full path used. > > > > Typical pg_dumpall output is: > > > > The program "pg_dump" is needed by pg_dumpall but was not found in the > > same directory as "/usr/

Re: [HACKERS] Strange code in initdb

2004-10-15 Thread Peter Eisentraut
Am Freitag, 15. Oktober 2004 06:24 schrieb Bruce Momjian: > I have modified these reports so they print the full path used. > > Typical pg_dumpall output is: > > The program "pg_dump" is needed by pg_dumpall but was not found in the > same directory as "/usr/local/postgres/bin/pg_dumpall". > Che

Re: [HACKERS] Strange code in initdb

2004-10-14 Thread Bruce Momjian
I have modified these reports so they print the full path used. Typical pg_dumpall output is: The program "pg_dump" is needed by pg_dumpall but was not found in the same directory as "/usr/local/postgres/bin/pg_dumpall". Check your installation.

Re: [HACKERS] Strange code in initdb

2004-10-12 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: > Shouldn't the second progname be argv[0] or something else that contains > the full path? argv[0] doesn't necessarily contain the full path. Is it worth calling find_my_exec() here to produce an absolute path? Possibly... r

[HACKERS] Strange code in initdb

2004-10-12 Thread Peter Eisentraut
What is this trying to tell us? if (ret == -1) fprintf(stderr, _("The program \"postgres\" is needed by %s " "but was not found in the same directory as \"%s\".\n" "Check your insta