| From: | Xuneng Zhou <xunengzhou(at)gmail(dot)com> |
|---|---|
| To: | Jingtang Zhang <mrdrivingduck(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Possible inaccurate description of wal_compression in docs |
| Date: | 2025-08-11 15:41:23 |
| Message-ID: | CABPTF7UG3ug281KLbpwwzcJP9VKzJmm4420Zk5gB9yPfuOHiNw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Sun, Aug 10, 2025 at 6:53 PM Jingtang Zhang <mrdrivingduck(at)gmail(dot)com> wrote:
>
> Hi hackers~
>
> I find the specification of wal_compression in our docs a little bit confusing
> for it 'compress full page images when FPW is on or during a base backup',
> which was true before v17. Since v17, we will also use full page images for
> creating index or table rewrites through bulk write, so it is inaccurate.
>
> Should we change the doc a little bit: 'compress full page images written
> to WAL, **like** when FPW is on, or during a base backup', if we may use
> FPI in other places in the future?
>
+1 for the update.
Best,
Xuneng
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2025-08-11 15:59:55 | Re: Possible inaccurate description of wal_compression in docs |
| Previous Message | Tom Lane | 2025-08-11 15:12:17 | Re: `pg_ctl init` crashes when run concurrently; semget(2) suspected |