Just to expound on Ezra's call.. There are replication solutions for Postgresql, but not as easy to use as MySQL. Just so you know, Skype uses Postgresql for their backend. http://highscalability.com/skype-plans-postgresql-scale-1-billion-users
- Ericson Smith CTO http://www.funadvice.com On Thu, May 22, 2008 at 3:33 PM, Raul <[EMAIL PROTECTED]> wrote: > > > ----- Original Message ----- > From: "Ezra Zygmuntowicz" <[EMAIL PROTECTED]> > To: <rubyonrails-deployment@googlegroups.com> > Sent: Thursday, May 22, 2008 12:19 PM > > > > > And I will agree that postgres is a better database then mysql in > > most cases> But I will still choose mysql for one major reason... > > replication. Postgres has no built in replication except for WAL file > > replication which means the slave is in recovery mode and you cannot > > run queries against it. If you are sure that you will never need to > > scale past one db server then psql is probably a better choice but if > > you will need to scale then mysql beats postgres hands down when it > > comes to master, slave and master master replication. > > > > This is excellent to know! Thanks > > Raul > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
