Hi All,

I'm in the process of setting up a Slony replicated cluster
at my organization, where we're running a postgresql-based
CMS application which is seriously chatty toward the db, and
therefore has some continuous on-going performance issues.

Now, I know that I can boost the performance of the app by
something like an order of magnitude on my development box
by turning fsync off in postgresql.conf, but obviously that
won't do for production.

But, it just occurred to me that if we're replicating the db
anyhow we could possibly turn fsync off for the master, but
leave it on on the slave(s), thereby having our fsynced logs
on the slave, while also enjoying the performance benifit on
the master.

Is this completely nuts?

Thanks!

-mark

-- 
--
=================================================================
-- mark at geekhive dot net --