If you don't do read queries on the slave than it will not have hot
data/pages/rows/tables/indexes in ram like the primary ? (it smoked weed
and was happy doing nothing so it was happy, but when responsibility came
(being promoted to master) it failed hard)
On Thu, May 15, 2014 at 6:46 AM, Kevin
On Thu, May 15, 2014 at 6:39 AM, Dorian Hoxha dorian.ho...@gmail.comwrote:
If you don't do read queries on the slave than it will not have hot
data/pages/rows/tables/indexes in ram like the primary ?
Yeah, that was the first thing we noticed, the cacti graph shows it took
two hours for the
We have a master/slave setup with replication. Today we failed over to the
slave and saw disk I/O go through the roof.
Are the pg_statistic statistics synced along with streaming replication?
Are you expected to have to do a vacuum analyze after failing over? That's
what we're trying now to see
