I've upgraded RubyForge to PostgreSQL 8.2. A couple of notes:
- The database is at about 18 million records
- It took around 6 minutes to dump and 8 minutes to restore.
- The dump/restore resulted in the disk space for the data directory going from 6.6 GB to 2.2 GB
- After the restore, I did a vacuumdb --full --analyze. That took around 3 minutes.
Overall, 8.2 seems great. I've got a little script that does a full record count; that script used to take around 2 minutes and now it runs in 5 or 6 seconds! And more importantly, the site seems snappy... good times.
What Pg did you upgrade from?
Posted by: Eric Hodel | December 12, 2006 at 02:30 PM
Hi Eric - upgraded from PostgreSQL 8.1.5.
Posted by: tomcopeland | December 12, 2006 at 02:32 PM
What hardware are you running?
Posted by: David Bird | December 12, 2006 at 05:44 PM
David - Complete hardware details are here:
http://rubyforge.org/docman/view.php/5/11/rubyforge_site_status.html
It's just a single box, dual CPUs, etc.
Posted by: tomcopeland | December 12, 2006 at 06:04 PM
How did you install 8.2 and get db:migrate to work. I have been trying to no avail. I put postgres 8.2 in the /usr/local/pgsql directory. Any ideas?
Posted by: Don Guernsey | December 26, 2006 at 11:51 PM
Don - RubyForge isn't a Rails app; it's running GForge (gforge.org). I am running other Rails apps on PostgreSQL 8.2 with no problems, though...
Posted by: tomcopeland | December 27, 2006 at 08:48 AM
Tom - I can't get it to work with Rails either, throws the error 'uninitialized constant ActiveRecord::Base::PGconn'
What version of Rails, what ruby postgres binding are you using?
Posted by: David Richardson | December 31, 2006 at 01:56 AM
Hi David - RubyForge is actually a PHP app - http://gforge.org/. But I'm using Rails 1.1.6 with PostgreSQL 8.2 and the native PostgreSQL bindings (version 0.7.1) on http://getindi.com/. Maybe it's your database.yml file; are you using "adapter: postgresql"? Also, did postgres.so build properly when you installed the postgres gem?
Posted by: tomcopeland | December 31, 2006 at 07:50 AM
For the record, turns out that the problem was with the postgres gem. It wasn't installing postgres.so, even though installation was reported as successful. I download the source code and installed from it.
Works fine - now I can go looking for those big Postgres 8.2 performance improvements ;-)
I presume the gem problem is something to do with the Fedora Core postgres library locations, but I'm not left with a lot of respect for the postgres gem.
Posted by: David Richardson | December 31, 2006 at 01:32 PM
Hi David - Yup, I've had to do the same thing... cd into the postgres gem directory and do a manual make. Weird. But yup, PostgreSQL 8.2 is an excellent piece of work... very snappy.
Posted by: tomcopeland | December 31, 2006 at 01:43 PM