Horton

Re: Different compression methods for FPI

x4mmm@yandex-team.ru

View thread View on postgr.es
From: Andrey Borodin <x4mmm@yandex-team.ru>
To: Michael Paquier <michael@paquier.xyz>
Cc: Justin Pryzby <pryzby@telsasoft.com>, Peter Eisentraut <peter.eisentraut@enterprisedb.com>, Heikki Linnakangas <hlinnaka@iki.fi>, pgsql-hackers <pgsql-hackers@postgresql.org>, Thomas Munro <thomas.munro@gmail.com>, Peter Geoghegan <pg@bowt.ie>, Andres Freund <andres@anarazel.de>
Date: 2021-06-17T08:18:52Z
Lists: pgsql-hackers 

> 17 июня 2021 г., в 11:57, Michael Paquier <michael@paquier.xyz> написал(а):
> 
> On Thu, Jun 17, 2021 at 11:45:37AM +0500, Andrey Borodin wrote:
>> Konstantin, Daniil and Justin are working on compressing libpq
>> [0]. That would make walsender compress WAL automatically.
>> And we (at least I and Dan) are inclined to work on compressing
>> on-disk WAL as soon as libpq compression will be committed.
> 
> What's the relationship between libpq and WAL?
walsender transmit WAL over regular protocol. Compressing libpq leads to huge decrease of cross-datacenter traffic of HA clusters.
In fact that's the reason why Daniil is working on libpq compression [0]. But that's matter of other thread.

Best regards, Andrey Borodin.

[0] https://www.postgresql.org/message-id/flat/161609580905.28624.5304095609680400810.pgcf%40coridan.postgresql.org#be6bc3ba77ff8a293b1816f4841c59ef

Commits

  1. Add more error context to RestoreBlockImage() and consume it

  2. Add support for LZ4 with compression of full-page writes in WAL

  3. Extended statistics on expressions

  4. Be clear about whether a recovery pause has taken effect.

  5. Add GUC to enable compression of full page images stored in WAL.