PQserverVersion not supported by this client version
Reported by Robby Russell | May 16th, 2008 @ 05:49 PM
Just upgraded to edge Rails and started to see this. It looks like the connection responds to server_version but libpq doesn't on my machine. Saw a few mentions of this on the old Rails Trac as well.
** Execute db:abort_if_pending_migrations
rake aborted!
PQserverVersion not supported by this client version.
vendor/rails/activerecord/lib/active_record/connection_adapters/postgresql_adapter.rb:795:in `server_version'
Comments and changes to this ticket
-
Robby Russell May 16th, 2008 @ 06:01 PM
I'm running PostgreSQL 8.2.6 via MacPorts on Leopard.
Gem: postgres (0.7.9.2008.01.09)
-
Tarmo Tänav May 16th, 2008 @ 07:19 PM
The error you're seeing should only exist in ruby-pg and not the postgres gem. The error is only compiled into ruby-pg if it determines your postgresql version to be older than 8.0. So you may want to make sure that you don't compile ruby-pg against an old version of libpq or just that you recompile ruby-pg.
Note that if you have both postgres and ruby-pg gems rails will prefer ruby-pg, I believe ruby-pg is the more actively developed one.
-
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Source available from github
The Git repository resides at http://github.com/rails
Check out the current development trunk (Edge Rails) with:
git clone git://github.com/rails/rails.git
Creating or reviewing a patch
See the contributor guide.
Creating a feature request
Please don't. If you want a new feature in Rails, you'll have to pull up your sleeves and get busy yourself. Or convince someone else to do it. See the contributor guide on how to get going. But posting them here is just going to lead to ticket root.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too".
