First WAL segment file that initdb creates

Fujii Masao <[email protected]> Wed, 9 Oct 2019 14:48:50 +0900

Newsgroups	gmane.comp.db.postgresql.devel.documentation
Message-ID	<CAHGQGwHOmGe2OqGOmp8cOfNVDivq7dbV74L5nUGr+3eVd2CU2Q@mail.gmail.com>

Hi,

There is the following description in wal.sgml.

    Segment
    files are given ever-increasing numbers as names, starting at
    <filename>000000010000000000000000</filename>.

But the first WAL segment file that initdb creates is 000000010000000000000001
not 000000010000000000000000. This change was caused by old commit 8c843fff2d,
but seems the documentation had not been updated unfortunately a long time.
Attached patch replaces 000000010000000000000000 with 000000010000000000000001
in the above description.

This patch needs to be back-patched to all the supported versions.

Regards,

-- 
Fujii Masao

first_wal_segment_v1.patch (application/octet-stream, 1007 B)

diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml
index 4eb8feb903..bd9fae544c 100644
*** a/doc/src/sgml/wal.sgml
--- b/doc/src/sgml/wal.sgml
***************
*** 758,764 ****
     are described in <filename>access/xlogrecord.h</filename>; the record
     content is dependent on the type of event that is being logged.  Segment
     files are given ever-increasing numbers as names, starting at
!    <filename>000000010000000000000000</filename>.  The numbers do not wrap,
     but it will take a very, very long time to exhaust the
     available stock of numbers.
    </para>
--- 758,764 ----
     are described in <filename>access/xlogrecord.h</filename>; the record
     content is dependent on the type of event that is being logged.  Segment
     files are given ever-increasing numbers as names, starting at
!    <filename>000000010000000000000001</filename>.  The numbers do not wrap,
     but it will take a very, very long time to exhaust the
     available stock of numbers.
    </para>