| From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: Different compression methods for FPI |
| Date: | 2021-06-16 08:52:50 |
| Message-ID: | 956D54DE-3347-46A8-BF00-AF585526FDF2@yandex-team.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 16 июня 2021 г., в 13:49, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> написал(а):
>
> Hmm, do we currently compress each block in a WAL record separately, for records that contain multiple full-page images? That could make a big difference e.g. for GiST index build that WAL-logs 32 pages in each record. If it helps the compression, we should probably start WAL-logging b-tree index build in larger batches, too.
Here's PoC for this [0]. But benchmark results are HW-dependent.
Best regards, Andrey Borodin.
https://www.postgresql.org/message-id/flat/41822E78-48EE-41AE-A89B-3CB76FF53980%40yandex-team.ru
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2021-06-16 09:05:08 | Re: Skipping logical replication transactions on subscriber side |
| Previous Message | Heikki Linnakangas | 2021-06-16 08:49:51 | Re: Different compression methods for FPI |