From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Geoghegan <pg@bowt.ie>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: harukat@sraoss.co.jp, pgsql-bugs@lists.postgresql.org, Andres Freund <andres@anarazel.de>
Subject: Re: BUG #18124: PG16 release note document bug in "Add build option to allow testing of small WAL segment sizes"
Date: Thu, 21 Sep 2023 22:08:18 -0400
Message-ID: <837536.1695348498@sss.pgh.pa.us> (raw)
In-Reply-To: <CAH2-Wzk+8CwQAaT1SSwQ1FmX-TNQEkw6QcndPYVc2Nd1v1DiMA@mail.gmail.com>
References: <18124-d363fa4873e176d6@postgresql.org>
<ZQzyO25k1xuHF4Ts@momjian.us>
<CAH2-Wzk+8CwQAaT1SSwQ1FmX-TNQEkw6QcndPYVc2Nd1v1DiMA@mail.gmail.com>
Peter Geoghegan <pg@bowt.ie> writes:
> On Thu, Sep 21, 2023 at 6:47 PM Bruce Momjian <bruce@momjian.us> wrote:
>> Uh, it is true that we don't have any segment sizes other than WAL, but
>> I am not sure people would easily know that, so I added WAL so people
>> knew.
> But the commit in question added a new option that can be used to
> control the relation segment size -- not the WAL segment size.
> Obviously, that's what TAKATSUKA-san meant.
Yeah. The release note entry is simply wrong to say it's WAL segment
size. I would also argue that d3b111e32's installation.sgml changes
were poorly worded, because they only say "segment size" which can
easily be misunderstood, just as happened here. Better would be
"relation segment size" or "table segment size".
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, pg@bowt.ie, bruce@momjian.us, andres@anarazel.de
Subject: Re: BUG #18124: PG16 release note document bug in "Add build option to allow testing of small WAL segment sizes"
In-Reply-To: <837536.1695348498@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox