Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZaFZd-0001tQ-9l for pgsql-docs@arkaria.postgresql.org; Fri, 11 Sep 2015 04:04:29 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZaFZc-0001xk-S3 for pgsql-docs@arkaria.postgresql.org; Fri, 11 Sep 2015 04:04:28 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZaFZI-0001ac-0I for pgsql-docs@postgresql.org; Fri, 11 Sep 2015 04:04:08 +0000 Received: from mail-io0-x22c.google.com ([2607:f8b0:4001:c06::22c]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1ZaFZF-0001jT-Jd for pgsql-docs@postgresql.org; Fri, 11 Sep 2015 04:04:06 +0000 Received: by iofh134 with SMTP id h134so85153713iof.0 for ; Thu, 10 Sep 2015 21:04:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=AdLFsQEmgxbv2UcTpbV2oCAkUZsop5GVlP3yS9AH8eM=; b=n5EvDL3ccZegK3v/pi+7HVBCKXJc+arVJiJHXsIKJgx/+4BAs/Dsj8ttW8viBECJ35 3DejpWFe/n4ywwd3bk9nqbVM3K3S4uNdymcN97MjiDJWpks1QUG4tR+RyFYzuRP6j2xZ RsRvLIqi1rRkXVt5XVF8/MHgw7qKcg0YJjT5iCDqMzBERt5Te0RBAeDbzXurU9oKfrix Q7D5+xGd9WEg8E+L3C9wyVjHdKeHFs230NYX615sEkWFNGnc/xtuxGxsL/L85HZI5Syy v/K3Nug/SXPGwEFOFdzYWyyVmPpDL5NLCzMJqxDfU+sOL787aNOlx7Tp+AxLGj4gGeRs 9WmQ== MIME-Version: 1.0 X-Received: by 10.107.10.91 with SMTP id u88mr178652ioi.136.1441944243815; Thu, 10 Sep 2015 21:04:03 -0700 (PDT) Received: by 10.79.116.135 with HTTP; Thu, 10 Sep 2015 21:04:03 -0700 (PDT) In-Reply-To: References: Date: Fri, 11 Sep 2015 13:04:03 +0900 Message-ID: Subject: Re: Possible mistake in Section 63.6 - 9.6devel Documentation From: Fujii Masao To: Michael Paquier Cc: Vignesh Raghunathan , pgsql-docs Content-Type: text/plain; charset=UTF-8 X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org On Thu, Sep 10, 2015 at 3:05 PM, Michael Paquier wrote: > On Thu, Sep 10, 2015 at 12:42 AM, Fujii Masao wrote: >> On Tue, Jul 21, 2015 at 9:59 AM, Michael Paquier >> wrote: >>> On Tue, Jul 21, 2015 at 6:54 AM, Vignesh Raghunathan >>> wrote: >>>> Hello, >>>> >>>> It has been mentioned in Section 63.6 that the first two fields in >>>> PageHeaderData track the most recent WAL entry related to the page. However, >>>> I am not sure how pd_checksum is related to WAL. Could it be possible that >>>> the sentence has been carried over from previous versions of the >>>> documentations without considering the change to the second field in >>>> PageHeaderData? >>> >>> Yes, the documentation is mistaken. The two bytes of pd_tli have been >>> switched to pd_checksum in 9.3, hence only the first field is relevant >>> for WAL, aka pd_lsn. Looking at this portion of the docs I think that >>> it should be updated as attached, mentioning pd_checksum as well. >> >> Also the type of pd_lsn in the Table 63-3 should be PageXLogRecPtr. > > Yep. See attached FWIW. Thanks! Applied. Regards, -- Fujii Masao -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs