On Mon, May 10, 2010 at 8:00 PM, Mike Christensen <mike@xxxxxxxxxxxxx> wrote: > The concept of updating one database and doing all your reads from > another database is kinda confusing to me. Does that mean you have to > design your whole app around that concept, have a different connection > string and what not for your "writable" database and "read-only > databases"? I'm using Castle ActiveRecord which I'm not even sure > supports that (without a ton of custom code anyway). > > Is there any sort of abstraction layer (like in the driver level) that > can abstract that and just make updates go to one DB and reads > round-robin to other DBs? Hopefully there's a way to make this design > simple to implement. Pretty sure pgpool can do the "read from these dbs, write to this one". -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
