Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 981101DACBC2 for ; Wed, 4 Jan 2012 13:55:07 -0400 (AST) Received: from [64.207.29.137] (helo=mail.illumen.com) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RiV3K-0007Pt-DM for pgsql-admin@postgresql.org; Wed, 04 Jan 2012 17:55:07 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: Re: Problem with pgstat timeouts Date: Wed, 4 Jan 2012 10:54:52 -0700 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ADMIN] Problem with pgstat timeouts Thread-Index: AczAx1kuxiLh9YPlTemUrggJRq7IwwKPqeDQ References: From: "Benjamin Krajmalnik" To: "Benjamin Krajmalnik" , "pgsql-admin" X-Host-Lookup-Failed: Reverse DNS lookup failed for 64.207.29.137 (failed) X-Pg-Spam-Score: 0.8 (/) X-Archive-Number: 201201/14 X-Sequence-Number: 38926 I have proceeded to do some more checking, and I see in iostat that the = pg_xlog drive has a significantly higher busy state than before. = Whereas it was barely busy when we first spun up the server (total %busy = since we started the server is about 6%) it is now in its 80's almost = steady state. We have a set of partitioned tables which are = continuously updated, and based on the size of them they no longer fit = in the shared memory which was allocated. Pg_xlog is in a SAS RAID 1. = The server is set up with streaming replication to an identical server. = The one thing which I just checked is the RAID mode on the server. db1# megacli64 -LDInfo -lAll -aAll =20 Adapter 0 -- Virtual Drive Information: Virtual Drive: 0 (Target Id: 0) Name : RAID Level : Primary-1, Secondary-0, RAID Level Qualifier-0 Size : 2.452 TB State : Optimal Strip Size : 256 KB Number Of Drives per span:2 Span Depth : 6 Default Cache Policy: WriteBack, ReadAhead, Direct, No Write Cache if = Bad BBU Current Cache Policy: WriteThrough, ReadAhead, Direct, No Write Cache if = Bad BBU Access Policy : Read/Write Disk Cache Policy : Disk's Default Encryption Type : None Virtual Drive: 1 (Target Id: 1) Name : RAID Level : Primary-1, Secondary-0, RAID Level Qualifier-0 Size : 418.656 GB State : Optimal Strip Size : 256 KB Number Of Drives : 2 Span Depth : 1 Default Cache Policy: WriteBack, ReadAhead, Direct, No Write Cache if = Bad BBU Current Cache Policy: WriteThrough, ReadAhead, Direct, No Write Cache if = Bad BBU Access Policy : Read/Write Disk Cache Policy : Disk's Default Encryption Type : None 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 back? Additionally, and somewhat unrelated, is there anything special which I = need to do when restarting the primary server vis-=E0-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?