From: Sean O'Grady <sean@thingee.com>
To: Jeff Janes <jeff.janes@gmail.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 13:32:13 -0400
Message-ID: <c36c4be478c2b271600a58281711e4add367d136@hey.com> (raw)
In-Reply-To: <CAMkU=1zR+w=Zjh_UKTs5hnD5LMRK0ct1uhZ6p3zNFmE_V_oYtw@mail.gmail.com>
> The internal compression has to compress each record in isolation,
> which is not nearly as good as compressing the entire file as there
> are patterns that exist between records not just within records.
I see, that's makes sense. My sense is that wal_compression is really
first to alleviate disk IO pressure and secondarily as a space saving
benefit. Since I've set about archive_timeout because of a relatively
light workload, I probably shouldn't need to worry about IO issues...
Thanks,
Sean
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, jeff.janes@gmail.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: <c36c4be478c2b271600a58281711e4add367d136@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