Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UWC5m-0002ob-5N for pgsql-admin@arkaria.postgresql.org; Sat, 27 Apr 2013 20:51:34 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1UWC5l-0002QI-H2 for pgsql-admin@arkaria.postgresql.org; Sat, 27 Apr 2013 20:51:33 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UWC5k-0002QD-Hd for pgsql-admin@postgresql.org; Sat, 27 Apr 2013 20:51:32 +0000 Received: from www.ipv6.roaringpenguin.com ([2607:f748:1200:fb:70:38:112:54] helo=colo3.roaringpenguin.com) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UWC5c-0002ns-EW for pgsql-admin@postgresql.org; Sat, 27 Apr 2013 20:51:32 +0000 Received: from vanadium.roaringpenguin.com ([192.168.10.23]) by colo3.roaringpenguin.com (8.14.3/8.14.3/Debian-9.4) with ESMTP id r3RKpK38008241 for ; Sat, 27 Apr 2013 16:51:20 -0400 Received: from shishi.roaringpenguin.com (dfs@shishi.roaringpenguin.com [192.168.2.3]) by vanadium.roaringpenguin.com (8.14.3/8.14.3/Debian-9.4) with ESMTP id r3RKpJJR003130 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Sat, 27 Apr 2013 16:51:19 -0400 Date: Sat, 27 Apr 2013 16:51:17 -0400 From: "David F. Skoll" To: pgsql-admin@postgresql.org Subject: Re: archive falling behind Message-ID: <20130427165117.396a2952@shishi.roaringpenguin.com> In-Reply-To: References: Organization: Roaring Penguin Software Inc. X-Mailer: Claws Mail 3.7.6 (GTK+ 2.20.1; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=roaringpenguin.com; h=date :from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=main; bh=Hk35Jn4v4E52 cM2ZfPTxVMo5MRs=; b=OT4XeHsCG169oJMQA0A5Q3SK7MJs129JqPqhSpFODlIj JTWpwMaWojHnAzKpELmLereSeak1fDp/8vZpJEXTbbe6/b4Wcpo6EPmzp9zuDjpk hlrssmgtxzxdIODLQhgraXVusWBCUREXgfsMH5ZC+Zmq+7MTMZLc97yWth75b3PD bIdJUNrVWjAwFskb1SFibF5VGMVMubtCA2ONUKF4vLDDxtMIrdSPxBKjZP0dcFJN iwwCUu7qb5buFSkFtep8OVGfQvzOWB0uQU9jldE8SwGRIlELasrGahq+Hgk011Sp QgldMp4LnHJ9vcivgfurxfGPZbyDpytpsT1zM0BCtA== X-Scanned-By: CanIt (www . roaringpenguin . com) X-Scanned-By: MIMEDefang 2.73 on 192.168.10.23 X-Spam-Score: undef - relay 192.168.10.23 marked with skip_spam_scan X-CanIt-Geo: No geolocation information available for 192.168.10.23 X-CanItPRO-Stream: outgoing (inherits from default) X-CanIt-Archive-Cluster: SQVyZJxqklY5buiWXYCN4T/BjiM X-CanIt-Archived-As: base/20130427 / 01Jt8PkDb X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org From: German Becker Subject: Re: archive falling behind > Actually this seems like a very strange filesystem /hw problem. The > wal segments keep "changing" even after I stoped the database and > noone is supposly accesing it: I've seen this before. It was bad RAM. I bet it's a hardware problem for you as well... either bad RAM or a flaky disk. In my case, I found it out because I got syntax errors in the PostgreSQL logs: SELGCT was not a valid keyword. It turns out that the flaky RAM was flipping bit 1 occasionally, so it would randomly add or subtract 2 from a byte. Regards, David. -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin