| From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | wenhui qiu <qiuwenhuifx(at)gmail(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Japin Li <japinli(at)hotmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Compression of bigger WAL records |
| Date: | 2025-07-14 18:22:32 |
| Message-ID: | 7F4307A0-0BFE-4B77-93B6-2FDD52F0586C@yandex-team.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 31 Jan 2025, at 08:37, wenhui qiu <qiuwenhuifx(at)gmail(dot)com> wrote:
>
> Hi Andery
> I have a question ,If wal_compression_threshold is set to more than the block size of the wal log, then the FPI is not compressed, and if so, it might make sense to have a maximum value of this parameter that does not exceed the block size of the wal log？
Oops, looks like I missed your question. Sorry for so long delay.
User might want to compress only megabyte+ records, there's nothing wrong with it. WAL record itself is capped by 1Gb (XLogRecordMaxSize), I do not see a reason to restrict wal_compression_threshold by lower value.
PFA rebased version.
Best regards, Andrey Borodin.
| Attachment | Content-Type | Size |
|---|---|---|
| v4-0001-Compress-big-WAL-records.patch | application/octet-stream | 42.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Álvaro Herrera | 2025-07-14 18:23:58 | Re: pg_dump does not dump domain not-null constraint's comments |
| Previous Message | Scott Mead | 2025-07-14 18:20:41 | Re: Disable parallel query by default |