| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: WAL compression and replica |
| Date: | 2024-03-25 20:21:11 |
| Message-ID: | 9435FDA8-261B-4E05-976C-6BB1EBC81815@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> On Mar 25, 2024, at 2:17 PM, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
> On Mon, Mar 25, 2024 at 1:10 PM Scott Ribe <scott_ribe(at)elevated-dev(dot)com> wrote:
> If WAL compression is enabled, does this mean that traffic to a file-based WAL-shipping standby is compressed? (In other words, WAL files are sent post-compression?)
>
> From the docs:
> When enabled, the PostgreSQL server compresses full page images written to WAL when full_page_writes is on or during a base backup.
>
> That is, some of the contents are compressed, it is not the container that gets compressed. That is always 64MB in a default compilation.
>
> David J.
I read that last week, and totally missed the implication. Thanks.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Uzair Khan | 2024-03-25 21:41:28 | Subject: Assistance Required: Adding Multiple Libraries to shared_preload_libraries in postgresql.conf |
| Previous Message | David G. Johnston | 2024-03-25 20:17:23 | Re: WAL compression and replica |