Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 48BFB2E00BB for ; Wed, 4 Jun 2008 08:07:51 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 15440-09 for ; Wed, 4 Jun 2008 08:07:44 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from gv-out-0910.google.com (gv-out-0910.google.com [216.239.58.191]) by developer.postgresql.org (Postfix) with ESMTP id 553712E00B2 for ; Wed, 4 Jun 2008 08:07:48 -0300 (ADT) Received: by gv-out-0910.google.com with SMTP id i36so12274gve.7 for ; Wed, 04 Jun 2008 04:07:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=gU88xwWVWkb8d6faFCmN59r1VIldhWHaq9NVaQc4xFc=; b=kj06QIEiXZ1Oa3EbeO/9gI3o2lqiUal3qSOHDTpPqpg86AANUBX/6BNw+8U62Ad+7J K6TuXsVh4kbjqSkj/7FUpwZ0Z0Ru98B/AEIfaKAilL5w9F0sq0hJSpW4n7ID5fhXBjD0 2yY/Pgq2kNzS/DuWerxglfLzhA80zpb7+knM8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=SvlvNHel8JjfIrUIrgGZrUZOBsa8xh6M7bDVmWPtQxeKjFrw9PiSR7P2yVnY9s7ZbL eoOCjAFPynaPpEQVDej5lfug8jUBS09tLDQx9KtyMIhs49jLLnhFQN3bcq8h43O11XhA 4sSgxnwTuocFWzZwPbmKXY9oy2XnEkq4cBcyI= Received: by 10.125.137.10 with SMTP id p10mr883319mkn.6.1212577665940; Wed, 04 Jun 2008 04:07:45 -0700 (PDT) Received: by 10.125.103.20 with HTTP; Wed, 4 Jun 2008 04:07:45 -0700 (PDT) Message-ID: Date: Wed, 4 Jun 2008 13:07:45 +0200 From: "rotellaro" To: pgsql-admin@postgresql.org Subject: Corrupted WAL during recovery from archived log MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200806/25 X-Sequence-Number: 29363 Hi, I'm writing some paper about instance recovery and I'm wondering how PostgreSQL act when find a corrupted archived WAL during the restore command. I found that when instance recovery starts the zero_damaged_pages is set to true. This parameter affect only data files with corrupted pages or even wal pages that are zeroed before going on data file? Thanks in advance Kind regards Federico -- (all opinions expressed are my own) Federico Campoli PostgreSQL Consulting -> PGHost http://www.pghost.eu