Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZZhW3-0006AP-3z for pgsql-docs@arkaria.postgresql.org; Wed, 09 Sep 2015 15:42:31 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZZhW2-0000Cu-Mg for pgsql-docs@arkaria.postgresql.org; Wed, 09 Sep 2015 15:42:30 +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 1ZZhW2-0000Cm-6V for pgsql-docs@postgresql.org; Wed, 09 Sep 2015 15:42:30 +0000 Received: from mail-ig0-x22b.google.com ([2607:f8b0:4001:c05::22b]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1ZZhW0-000271-12 for pgsql-docs@postgresql.org; Wed, 09 Sep 2015 15:42:29 +0000 Received: by igbkq10 with SMTP id kq10so107639763igb.0 for ; Wed, 09 Sep 2015 08:42:27 -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=mFsYNCpuBLfy6BUO6gpuM0znXsAAIZi4IODBqC641UU=; b=CjFt9WsfLwg+/LuhzZRCdDg28aIWyHuRFFbmfWvKncbByqJGijI6rkXkydfJ+Mpb0S siEeEDrNXGlGy6rBsAKs6CjhF7QmNYbfXMy84AWCGepvB/ljTpwPyza+MmfHYGElTN8w i5QDVYEvClNKzfWmhc0et6NWqs+ApTw1LkL1DZAeDrFDeNstJCpmHBM3Opew7jgGsnW2 AvZjITHT3ihr92lltI41aG7AsWAgoYdiWumnqM+f7CxoGNg748bweUGdp1OCS9FMnblu Ut+eQlk71rFp0/AIY9lCRP0d7f8qaKLmuMretgB2ugb5CmYJqJB843wX75j8C6bIEE3o KCtQ== MIME-Version: 1.0 X-Received: by 10.50.17.34 with SMTP id l2mr4572361igd.58.1441813347351; Wed, 09 Sep 2015 08:42:27 -0700 (PDT) Received: by 10.79.116.135 with HTTP; Wed, 9 Sep 2015 08:42:27 -0700 (PDT) In-Reply-To: References: Date: Thu, 10 Sep 2015 00:42:27 +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 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. 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