Re: BUG #18124: PG16 release note document bug in "Add build option to allow testing of small WAL segment sizes"
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Geoghegan <pg@bowt.ie>
Cc: Bruce Momjian <bruce@momjian.us>, harukat@sraoss.co.jp,
pgsql-bugs@lists.postgresql.org, Andres Freund <andres@anarazel.de>
Date: 2023-09-22T02:08:18Z
Lists: pgsql-bugs
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
Commits
-
docs: Clarify --with-segsize-blocks documentation
- 72bf3f0877fe 16.1 landed
- a2c2fbf740fc 17.0 landed