This is driving me nuts
First, my hosting provider that I have been with since the stone age, are dragging their feet about updating to Centos 6 and, from what I have read, I can see why.
Instead of waiting for the next ice age to pass, I read the instructions for just updating postgresql 9.2 on Centos 5, which is all I need to run my bundle install, which tells me that my PostgreSQL is too old - PostgreSQL 8.1.23
After updating and starting, here's the message back:
[root@vps data]# /etc/init.d/postgresql-9.2 start
/etc/rc.d/init.d/functions: fork: Cannot allocate memory
/etc/profile.d/lang.sh: line 53: /sbin/consoletype: Argument list too long
Starting postgresql-9.2 service: [ OK ]
It started, great - right?
No,
[root@vps data]# psql --version
psql (PostgreSQL) 8.1.23
contains support for command-line editing
If 9.2 started, then why does it still say 8.1.23?
Maybe I just need to reboot
reboot -i
ssh back in psql --version still shows PostgreSQL 8.1.23 - WTF?
I run /etc/init.d/postgresql-9.2 start - it starts - OK, cool
bundle install
Make sure that `gem install pg -v '0.17.1'` succeeds before bundling
gem install pg -v '0.17.1'
I still receive the error:
checking for PQconnectionUsedPassword()... no
Your PostgreSQL is too old. Either install an older version of this gem or upgrade your database.
*** extconf.rb failed ***
So, my ultimate questions are:
If the postgresql 9.2 started, why does it say that I am running 8.1.23?
Do I have to rm -rf the entire /usr/bin/psql and start over?