On Fri, April 4, 2008 11:23 pm, stuntmusic wrote:
> I have an office that works on the master database of our application and
> I
> want to set up a way for these users to work on a slave DB to keep them
> off
> the production 'wire'

Try using slony with PgPool - pgpool can intercept mods
(update/insert/delete) and send them to the master, while selects stay on
the slave.  Slony then takes care of replicating those changes back to the
slave/s.

We used this setup for months for exactly the same reason - reducing load
on the master (big selects), while reducing bandwidth use over a WAN line.

Let me know if you decide to go this way and I'll send you a typical
pgpool config.

Regards
Henry