Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 17D1712822D8 for ; Wed, 22 Feb 2012 16:38:56 -0400 (AST) Received: from mail-pz0-f46.google.com ([209.85.210.46]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1S0Ixk-0005sB-10 for pgsql-admin@postgresql.org; Wed, 22 Feb 2012 20:38:56 +0000 Received: by daed14 with SMTP id d14so417566dae.19 for ; Wed, 22 Feb 2012 12:38:42 -0800 (PST) Received-SPF: pass (google.com: domain of brianf@consistentstate.com designates 10.68.134.226 as permitted sender) client-ip=10.68.134.226; Authentication-Results: mr.google.com; spf=pass (google.com: domain of brianf@consistentstate.com designates 10.68.134.226 as permitted sender) smtp.mail=brianf@consistentstate.com Received: from mr.google.com ([10.68.134.226]) by 10.68.134.226 with SMTP id pn2mr65460669pbb.18.1329943122908 (num_hops = 1); Wed, 22 Feb 2012 12:38:42 -0800 (PST) Received: by 10.68.134.226 with SMTP id pn2mr54171487pbb.18.1329943122852; Wed, 22 Feb 2012 12:38:42 -0800 (PST) Received: from sidon.consistentstate.com (173-164-51-9-colorado.hfc.comcastbusiness.net. [173.164.51.9]) by mx.google.com with ESMTPS id u9sm19830451pbj.39.2012.02.22.12.38.41 (version=SSLv3 cipher=OTHER); Wed, 22 Feb 2012 12:38:42 -0800 (PST) Message-ID: <4F45517F.4050508@consistentstate.com> Date: Wed, 22 Feb 2012 13:35:11 -0700 From: Brian Fehrle User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.2.26) Gecko/20120129 Lightning/1.0b2 Thunderbird/3.1.18 MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: WAL files containing old and unmodified data? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQmCHA6H4AS2qYoIc7z6ucHPBB+E4CPx4RxDuJ5rj86CPOKP/4ZFuS9tazmQ+RYCi9l6QKAC X-Pg-Spam-Score: -2.6 (--) X-Archive-Number: 201202/88 X-Sequence-Number: 39148 Hi all, I have a very active database that generates between 200 and 400 WAL files that are archived for backups. Yesterday, the average number of WAL files being generated skyrocketed. We took a look at some WAL files using the strings command, and notice quite a bit of data from a specific table with timestamps of last year. This table does some basic tracking, where a row is inserted, then it's updated, and after that it's never modified again. So we're having data appear in our WAL files from rows that haven't (or should not have been) modified at all in over a year. We figured that the rows were in fact being updated, so we turned log_min_duration_statement to 0 for a period of time and monitored all queries going through, however we never found a single query that could possibly be updating these pieces of data. Is there any other reason why a WAL file could contain data that (we believe) hasn't changed? Or is the fact that it's in the WAL file a guarantee that the data is either changed or new? Can server processes such as autovacuum processes cause this behavior? Anywhere else I should try to look? Thanks in advance, - Brian F