On Mon, Jul 6, 2009 at 10:26 PM, Jared Still <jkst...@gmail.com> wrote:
> > On Mon, Jun 29, 2009 at 7:59 PM, Bill Moseley <mose...@hank.org> wrote: > >> What solutions are available, if any, to work with a master and multiple >> slave database configuration that would be transparent to the application? >> That is, send all select requests to the slaves but writes, and explicit >> transactions (begin, select for update) go to the master. Database is >> Postgresql. >> > > The obligatory question: > > What are you really trying to accomplish? Sorry if that wasn't clear. The goal is to reduce load on the database. Using Slony replication with a single master and multiple slaves we want the application to transparently send selects to the pool of slaves, but any updates (and transactions) must go to the master. Slony replication is asynchronous so after a write all selects go to master for a configured amount of time to allow slaves to sync. The goal of this email was to see if anyone is doing something similar. > > > > Jared Still > Certifiable Oracle DBA and Part Time Perl Evangelist > > > -- Bill Moseley mose...@hank.org
