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>, Dilip Kumar <dilipbalaut@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>, Thomas Munro <thomas.munro@gmail.com>
Date: 2021-06-28T08:01:00Z
Lists: pgsql-hackers 

> 28 июня 2021 г., в 12:36, Michael Paquier <michael@paquier.xyz> написал(а):
> 
> Removing "allows_streaming => 1" in 011_crash_recovery.pl is enough to
> make the test fail on HEAD.  And the test fails equally without or
> without any changes related to wal_compression, so adding or removing
> options to wal_compression is not going to change anything with that.
> There is simply no relationship I can spot, though I may be missing of
> course an argument here.  
There is no relationship at all. That test 011_crash_recovery.pl is failing depending on random fluctuation in WAL size. Currently, it does not affect this thread anyhow (except for confusion I made by importing patch with fix from other thread, sorry).


> Let's just discuss this recovery issue where
> it should be discussed (these are patches 0002 and 0003 in the patch
> v9 sent upthread):
> https://www.postgresql.org/message-id/20210308.173242.463790587797836129.horikyota.ntt%40gmail.com
+1.

Best regards, Andrey Borodin.

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.