Skip site navigation (1) Skip section navigation (2)

Re: Problem with pgstat timeouts

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "pgsql-admin" <pgsql-admin(at)postgresql(dot)org>, "Benjamin Krajmalnik" <kraj(at)servoyant(dot)com>
Subject: Re: Problem with pgstat timeouts
Date: 2012-01-04 18:43:59
Message-ID: 4F04498F020000250004438B@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-admin
"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)?
 
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

In response to

Responses

pgsql-admin by date

Next:From: Benjamin KrajmalnikDate: 2012-01-04 18:48:02
Subject: Re: Problem with pgstat timeouts
Previous:From: Tom LaneDate: 2012-01-04 18:14:04
Subject: Re: Cannot restore dumps made with -Fc and --column-inserts

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group