"Benjamin Krajmalnik" <kraj(at)servoyant(dot)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)?
> If this is the case, would it be safe to change the cache to Write
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.
In response to
pgsql-admin by date
|Next:||From: Benjamin Krajmalnik||Date: 2012-01-04 18:48:02|
|Subject: Re: Problem with pgstat timeouts|
|Previous:||From: Tom Lane||Date: 2012-01-04 18:14:04|
|Subject: Re: Cannot restore dumps made with -Fc and --column-inserts |