Rails on PostgreSQL : Rails apps using PostgreSQL in production

Comment on Rails apps using PostgreSQL in production by alex@alexkane.net

Thu, 17 Sep 2009 16:45:37 +0000

I’m about to launch a PostgreSQL powered rails app, will post the URL when it’s launched.

Comment on Rails apps using PostgreSQL in production by Tom Copeland

Thu, 17 Sep 2009 17:03:00 +0000

@alex, cool, sounds good!

Comment on Rails apps using PostgreSQL in production by Marc Tremblay

Thu, 17 Sep 2009 20:06:47 +0000

We have a Rails + PostgreSQL application, currently in closed beta, at http://screenlight.tv

Comment on Rails apps using PostgreSQL in production by Nathen Harvey

Fri, 18 Sep 2009 08:09:04 +0000

VisualCV - http://www.visualcv.com is on PostgreSQL

Comment on Rails apps using PostgreSQL in production by Tom Copeland

Fri, 18 Sep 2009 09:48:52 +0000

@nathen, @marc, thanks guys! Any technical details you can add? Replication solutions, full text search, any oddities you ran into, anything like that would be appreciated!

Comment on Rails apps using PostgreSQL in production by Ryan Heneise

Thu, 01 Oct 2009 15:43:09 +0000

Donor Tools (www.donortools.com) has been happily running on PostgreSQL in production for over a year.

Comment on Rails apps using PostgreSQL in production by Exchange

Thu, 30 Sep 2010 02:33:23 +0000

It depends on the projected scale of your web application. For relatively small databases, MySQL is fine and is slightly faster for simple selects, etc. Once your database gets large however, MySQL hits a wall where PostgreSQL just keeps on driving through it.

As long as you’re using ActiveRecord for your middleman, it won’t matter what database you use, as it builds Standards Compliant SQL Statements, which will work on both databases. As soon as you specify any triggers, stored procedures, etc, you’ll be stuck with one database.

I personally prefer PostgreSQL, but that’s just because I was never a big fan of MySQL.