| From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
|---|---|
| To: | Fabrice Chapuis <fabrice636861(at)gmail(dot)com> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: wal_compression |
| Date: | 2025-01-20 10:31:44 |
| Message-ID: | CAECtzeVxT95ahfH2ire6YgdDKvuuHB+2O_eCQJuQTib8KA8K3g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hi,
Le lun. 20 janv. 2025 à 11:23, Fabrice Chapuis <fabrice636861(at)gmail(dot)com> a
écrit :
> In Postgres 17 doc, for wal_compression parameter it's written:
> "Turning this parameter on can reduce the WAL volume without increasing
> the risk of unrecoverable data corruption"
> If wal_compression = on then when a full page is written in the wal, it
> will be compressed. What I do not understand is that the wal file keeps the
> same size 16Mb. What is the interest to activate wal_compression?
>
>
A WAL file contains some records. Usually a lot of records. If a record is
compressed, it will take less space in the WAL file. Hence, this WAL file
will contain more records, and you will need less WAL files for the same
activity.
--
Guillaume.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Siraj G | 2025-01-20 11:07:11 | Re: Performance issue - Seq Scan |
| Previous Message | Fabrice Chapuis | 2025-01-20 10:22:46 | wal_compression |