From: Scott Ribe <scott_ribe@elevated-dev.com>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: WAL compression and replica
Date: Mon, 25 Mar 2024 14:21:11 -0600
Message-ID: <9435FDA8-261B-4E05-976C-6BB1EBC81815@elevated-dev.com> (raw)
In-Reply-To: <CAKFQuwYQX9bKp+4GDU+yzB_CkjHiAsft_Y9_Q7L1Q4+v8Ncs7g@mail.gmail.com>
References: <E0F4D22D-5B4F-4867-84FF-740F8AB87E6C@elevated-dev.com>
<CAKFQuwYQX9bKp+4GDU+yzB_CkjHiAsft_Y9_Q7L1Q4+v8Ncs7g@mail.gmail.com>
> On Mar 25, 2024, at 2:17 PM, David G. Johnston <david.g.johnston@gmail.com> wrote:
>
> On Mon, Mar 25, 2024 at 1:10 PM Scott Ribe <scott_ribe@elevated-dev.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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott_ribe@elevated-dev.com, david.g.johnston@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: WAL compression and replica
In-Reply-To: <9435FDA8-261B-4E05-976C-6BB1EBC81815@elevated-dev.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox