Man that sounds awesome. I need that now. So does that mean you'd have one beefy SQL server for all the updates and everything writes to that, and then you'd have a bunch of read-only servers and new data trickles into them from the master continuously? Mike On Mon, May 10, 2010 at 6:09 PM, Scott Marlowe <scott.marlowe@xxxxxxxxx> wrote: > On Mon, May 10, 2010 at 7:04 PM, Mike Christensen <mike@xxxxxxxxxxxxx> wrote: >> Thanks for the advice. In that case, I'll stick with the standard >> approach of having a single SQL server and several web frontends and >> employ a caching mechanism such as memcache as well. Thanks! > > And with 9.0 it will be pretty easy to setup hot read PITR slaves so > you can build a pretty simple failover system. > -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
