Having done two fairly large sites; one in PostGres and one in MySQL the primary differences I noticed were:
* PostGres doesn't have locking issues, but this comes at the expense of having to "compact" it (or whatever it was called, this was a few years ago). If you don't do this fairly often on a DB with constant updates your DB grinds to a halt. * MySQL seems to have a more straightforward approach to scaling up. The whole master/slave/server-farm stuff is pretty built into MySQL. Not so with PostGres... there were ways to do this but none were very easy. I'm not an expert in either of these but, those were my experiences on those projects. I think I'd lean towards MySQL going forwards. -ben On Mon, Jan 25, 2010 at 5:42 AM, Robert Postill < [email protected]> wrote: > I'm a Postgres supporter so I'll tell you some of my perceived > Postgres benefits and then you can pick that apart :) > > * Postgres has a BSD license which makes it easier to work with > commercially than MySQL sometimes > * Postgres can perform better in a SAN configuration due to its > asynchronous I/O implementation, in general Postgres scales up better > than MySQL > * Postgres can be configured to work with the mandatory security > features of selinux (http://code.google.com/p/sepgsql/), I saw a talk > at LCA last year where the presenter used selinux to provide column > masks over sensitive data > * Postgres has a rich set of extension languages for working with the > DB including PL/Ruby, handy for those large batch ops and for the > ports from Oracle > * Postgres has a rich type system and sql syntax (erm I'm prepared to > be corrected but I believe both are superior to MySQL's) > * PostGIS (http://postgis.refractions.net/) is a great piece of software > > None of these makes a damn bit of difference if you're in many rails > apps :) I started using Postgres because the SQL was closer to > Oracle's. > > Rob > > 2010/1/25 Cameron Barrie <[email protected]>: > > > > On 25/01/2010, at 5:38 PM, Xavier Shay wrote: > > > >> On 25/01/10 12:35 PM, Jason Stirk wrote: > >>> ... Deployment database? > >>> MySQL, recently played a bit with Postgres (although I'm still > unimpressed) > >> This is contrary to most opinion I've heard, so I'm interested in > hearing more. > > Me too actually. > >> > >> Xav > >> > >> -- > >> You received this message because you are subscribed to the Google > Groups "Ruby or Rails Oceania" group. > >> To post to this group, send email to [email protected]. > >> To unsubscribe from this group, send email to > [email protected]<rails-oceania%[email protected]> > . > >> For more options, visit this group at > http://groups.google.com/group/rails-oceania?hl=en. > >> > > > > -- > > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > [email protected]<rails-oceania%[email protected]> > . > > For more options, visit this group at > http://groups.google.com/group/rails-oceania?hl=en. > > > > > > > > -- > > Charles de Gaulle - "The better I get to know men, the more I find > myself loving dogs." - > http://www.brainyquote.com/quotes/authors/c/charles_de_gaulle.html > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<rails-oceania%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rails-oceania?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
