Re: Possible inaccurate description of wal_compression in docs
Xuneng Zhou <xunengzhou@gmail.com>
From: Xuneng Zhou <xunengzhou@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Andrey Borodin <x4mmm@yandex-team.ru>,
Jingtang Zhang <mrdrivingduck@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>,
pgsql-hackers@lists.postgresql.org
Date: 2025-08-13T05:33:26Z
Lists: pgsql-hackers
Hi, On Tue, Aug 12, 2025 at 12:41 PM Michael Paquier <michael@paquier.xyz> wrote: > On Mon, Aug 11, 2025 at 06:59:55PM +0300, Andrey Borodin wrote: > > FPWs are used here and there in a lot of places, like "FPI for > > hint". And indexes are build using FPI for many years, it did not > > start with 17... > > This list is not exhaustive in any case, so I agree that formulation > > should not be very strict. > > Perhaps, yes, the formulation used in this paragraph could be a bit > more evasive. What we do not want is to keep a wording that would > require more maintenance each time the internals of the backend are > changed, so adding an extra "like" may be OK. > > Do any of you have a specific wording in mind? > > "Like" LGMT. Best, Xuneng
Commits
-
doc: Improve description of wal_compression
- 3f134ce7001b 13.23 landed
- 24145bbb9e6c 14.20 landed
- 1c58a1bba437 15.15 landed
- d16ed88f040b 16.11 landed
- dc8efd61d929 17.7 landed
- 859444465f74 18.0 landed
- b5d87a823f2f 19 (unreleased) landed