On Sun, 23 Jan 2005 09:46:29 +0200, Jarkko Elfving <jarelf@xxxxxxxxxx> wrote: > On Sun, 2005-01-23 at 02:15 -0500, Tom Lane wrote: > > Uh, /var/lib/pgsql should have been created for you by RPM installation. > > I'm starting to think you have a corrupted postgresql-server RPM. > > > > Also, in your prior message: > > > > > bash-3.00$ initdb -D=/var/lib/pgsql/data/ > > > fgets failure: Success > > > The program "postgres" is needed by initdb but was not found in the > > > same directory as "/usr/bin/initdb". > > > Check your installation. > > > > As best I can tell from the source code, this could only happen if > > "/usr/bin/postgres -V" failed. What happens if you do that by hand? > > What does "ls -l /usr/bin/postgres" show? > > > > regards, tom lane > > > > Yes, I noticed that RPM did a folder /var/lib/pgsql but I was thinking > 'coz I didn't get it worked that in easy way, I start to read some of > Postrge instructions where was telling to do this. Anyway, I check what > ls -l /usr/bin/postgres tells me, and result were expected: > > # ls -l /usr/bin/postgres > -rwxr-xr-x 1 root root 2541272 Jan 18 11:31 /usr/bin/postgres > > Also I run a /usr/bin/postgres -V but this doesn't give any results. > > I'm quite new on Linux. I'm thinking you're trying to hack too much on your own that the RPMs do automagically. All you should need to do is install the RPMs, start postgresql with the provided init script, and be good to go. I'd suggest uninstalling all postgresql RPMs, deleting /var/lib/pgsql, reinstalling the RPMs and then just start /etc/init.d/postgresql. If that fails to work, then set PGLOG in /etc/init.d/postgresql to something other than /dev/null and try starting again. Then check the log for why its failing. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ L. Friedman netllama@xxxxxxxxx LlamaLand http://netllama.linux-sxs.org ---------------------------(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
