"Benjamin Krajmalnik" <k...@servoyant.com> wrote: > Default Cache Policy: WriteBack, ReadAhead, Direct, No Write Cache > if Bad BBU > Current Cache Policy: WriteThrough, ReadAhead, Direct, No Write > Cache if Bad BBU > Is it possible that the WriteThrough is what is causing the high > io (and maybe the pgstat wait timeouts as well)? Yes. > If this is the case, would it be safe to change the cache to Write > back? Maybe. How did it get into this (non-default) state? Are batteries installed and healthy? > Additionally, and somewhat unrelated, is there anything special > which I need to do when restarting the primary server vis-à-vis > the streaming replication server? In other words, if I were to > restart the main server, will the streaming replication server > reconnect and pick up once the primary comes online? I think that should be pretty automatic as long as you haven't promoted the standby to be the new master. -Kevin
-- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
