> [Charset ISO-8859-1 unsupported, filtering to ASCII...]
> > Tom Lane writes:
> >
> > > Or possibly he's invoking the right initdb, but it's finding the wrong
> > > postgres binary.
> >
> > Or the wrong template files? Run initdb --show to see.
> >
> > > I wonder if we can get initdb to check that it's
> > > invoking the right version of 'postgres'? A display of the version
> > > number wouldn't be a bad idea either.
> >
> > I know I might have had a different opinion on this before but I'm
> > beginning to think that the path to any auxiliary programs needs to be
>
> I understand your concern. My question is how does someone access
> initdb without getting binaries of the same version?
>
> Seems it may be happening, but how?
>
This happened to me in v6.5.3, and the problem was/is that the path
setting in the install instructions is incorrect.
In the INSTALL file that came with v6.5.3:
Step 17, line 441: PATH=$PATH:/usr/local/pgsql/bin
is no good (at least for RH6.0, 6.1, shell=bash). RH's default
install of postgres puts the binaries in /usr/bin, which is then ahead
of /usr/local/pgsql/bin in the path. Thus, the newly created binaries
aren't found.
The line should be:
PATH=/usr/local/pgsql/bin:$PATH
I'm sorry I didn't file a bug report after I figured it out, but since
I've got finals I should be studying for, now seems like a good time ;)
Tucker
