You are correct. But the original poster mentioned Postgresql, and I just thought I would share my experiences on a similar stack that he's considering.
I also use MySQL on other projects along with Postgresql. - Ericson Smith On 3/13/07, Rob Sanheim <[EMAIL PROTECTED]> wrote: > > On 3/13/07, Ericson Smith <[EMAIL PROTECTED]> wrote: > > > > One of the downsides of Postgres with the typical PHP stack is > > connection latency. > > > > We actually switched from MySQL to Postgres on > > http://www.funadvice.com and the site was faster and more stable. > > Running Rails in production mode keeps a persistent connection open to > > Postgres for each mongrel running. > > Isn't this usually how mysql and rails would work? Usually mysql will > let a connection 'sleep' a certain amount of time, so the connection > doesn't need to be reopened for each request. You can configure the > sleep time, but I would guess any normal setting like 60 seconds would > be more then enough for the connection to hang out open for rails to > continue to reuse. > > - Rob > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
