Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eiiQV-0008V6-WD for pgsql-admin@arkaria.postgresql.org; Mon, 05 Feb 2018 15:11:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eiiQU-0003LF-UV for pgsql-admin@arkaria.postgresql.org; Mon, 05 Feb 2018 15:11:22 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eiiQU-0003L6-NK for pgsql-admin@lists.postgresql.org; Mon, 05 Feb 2018 15:11:22 +0000 Received: from omr2.cc.ipv6.vt.edu ([2607:b400:92:8400:0:33:fb76:806e] helo=omr2.cc.vt.edu) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eiiQQ-0006st-5w for pgsql-admin@lists.postgresql.org; Mon, 05 Feb 2018 15:11:22 +0000 Received: from mr6.cc.vt.edu (mr6.cc.ipv6.vt.edu [IPv6:2607:b400:92:8500:0:af:2d00:4488]) by omr2.cc.vt.edu (8.14.4/8.14.4) with ESMTP id w15FBFwG012209 for ; Mon, 5 Feb 2018 10:11:15 -0500 Received: from mail-qt0-f198.google.com (mail-qt0-f198.google.com [209.85.216.198]) by mr6.cc.vt.edu (8.14.7/8.14.7) with ESMTP id w15FBA9p010351 for ; Mon, 5 Feb 2018 10:11:15 -0500 Received: by mail-qt0-f198.google.com with SMTP id a21so25864278qtd.6 for ; Mon, 05 Feb 2018 07:11:15 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=K5slQ5U8evWsmwaq6KR6dcibBzhDyGpxiL5YDlxoO8c=; b=G3CsNBhPHwY+iUg+zkrlBqmcpLABwPgYBNnjkm/evGpTYhJYlTJzRgt+RmFdoIRViH VMZyD8b3QZdsexYkc+jjO+q+AWhhLsgvc9ANJJcJR6ldJ/o/UxIc1IX4CBTJAVhKnH2Z bTBcgC7z4VZ87EWif5CfAIwHC+V39C7iK1hT0GGvbu7ZJaz3IQdxjCq6wqWJSsFyvV3d Sp5Tgcw6/Z2vuNEcro+TVKJqR1CaPKLaIHWiHhDnOH07YY3xGA7cT3yGOeqaTNfAv/eI bSmlXIIaR/Q4K7A3Usj5CPbPNvaWCjWDSEz1QrzJoc5vNL/dyAH74ZYTS7ycpMc0Gm7Q MZ+w== X-Gm-Message-State: AKwxytdaTU3YMgY9xEL/PQL5twLm5+7geD1Pw8ycEonhuFmkqRCftnNb JJieX+dqC5/9ZZeXZQG4VxajTsVx+uPn1kUyT1DwygjSMOqZ2od9Qclw2KhzPXKu8ZLrk6f8ZM6 B8ULe1pmlD3v39im/HyI49Qc78bvEUE0oYg2lI2bpKNpHXvqP55xoAB8gqjRfvQx9OF0rlfooh2 09BHEcgNei X-Received: by 10.237.48.2 with SMTP id 2mr77295604qte.232.1517843470253; Mon, 05 Feb 2018 07:11:10 -0800 (PST) X-Google-Smtp-Source: AH8x2275EM1mvj6JedMgnR8ocoSwoSgA2IO1vHhMur3TM76b0eUSoL3ppFe2Xd8wC6vVvZCe3ZALsQ== X-Received: by 10.237.48.2 with SMTP id 2mr77295582qte.232.1517843470044; Mon, 05 Feb 2018 07:11:10 -0800 (PST) Received: from stell.cns.vt.edu ([2001:468:c80:2102:ad8e:dd73:7522:537e]) by smtp.gmail.com with ESMTPSA id s7sm5769746qkd.67.2018.02.05.07.11.09 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Feb 2018 07:11:09 -0800 (PST) Subject: Re: uninitialized page in standby recovery From: Ray Stell To: pgsql-admin@lists.postgresql.org References: Message-ID: Date: Mon, 5 Feb 2018 10:11:08 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2/5/18 9:06 AM, Ray Stell wrote: > I built a standby with 9.4.12 and about a day later the standby > crashed with this: > > 2018-02-02 16:20:44 EST,0, WARNING:  page 1347460 of relation > base/16391/16414 is uninitialized > 2018-02-02 16:20:44 EST,0, CONTEXT:  xlog redo visible: rel > 1663/16391/16414; blk 1347460 > 2018-02-02 16:20:44 EST,0, PANIC:  WAL contains references to invalid > pages > 2018-02-02 16:20:44 EST,0, CONTEXT:  xlog redo visible: rel > 1663/16391/16414; blk 1347460 > 2018-02-02 16:20:44 EST,0, LOG:  startup process (PID 24057) was > terminated by signal 6: Aborted > 2018-02-02 16:20:44 EST,0, LOG:  terminating any other active server > processes > > Any hints to where the corruption begins?  I don't see any disk i/o > issues.  Not sure what to look for in the release notes, > > but I'll try to patch asap, but that is difficult to get done > politically. > looks like bug 13822, discussed here: https://www.postgresql.org/message-id/20151217125025.6916.26898%40wrigleys.postgresql.org This discuss is in 9.4.5, how can I follow the thread?  Is there a bug db to query?