From: Sean O'Grady <sean@thingee.com>
To: Scott Ribe <scott_ribe@elevated-dev.com>
Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Cc: Wetmore, Matthew (CTR) <matthew.wetmore@express-scripts.com>
Subject: Re: Question about wal_compression and what to expect
Date: Wed, 21 Jun 2023 10:04:28 -0400
Message-ID: <1c92a69086aa7046c2141a3849b1eff92eb68a37@hey.com> (raw)
In-Reply-To: <CDC433EB-E5B0-46CC-AD36-4957419B517C@elevated-dev.com>
With archive_timeout set I think WAL files will often (at least in my
case) be created before they are filled, and in those cases there should
be a larger benefit, correct?
Thanks
On June 21, 2023, Scott Ribe <scott_ribe@elevated-dev.com> wrote:
> > On Jun 21, 2023, at 7:51 AM, Sean O'Grady <sean@thingee.com> wrote:
> >
> > Yes, my question was essentially do I need to separately compress
> WAL files for storage/archiving even with wal_compression set. So, I
> think you've answered my question.
>
> If WAL files use per-page compression internally, you won't get much
> benefit from compressing them. If they use lz4 internally, then sure,
> bzip'ing them will get a little benefit, but nowhere near the normal
> amount.
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: sean@thingee.com, scott_ribe@elevated-dev.com, pgsql-admin@lists.postgresql.org, matthew.wetmore@express-scripts.com
Subject: Re: Question about wal_compression and what to expect
In-Reply-To: <1c92a69086aa7046c2141a3849b1eff92eb68a37@hey.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