| From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Subject: | Re: Different compression methods for FPI |
| Date: | 2021-06-28 08:01:00 |
| Message-ID: | 9C189C4C-167E-47B5-8E95-F57CFBECD0D8@yandex-team.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 28 июня 2021 г., в 12:36, Michael Paquier <michael(at)paquier(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2021-06-28 08:13:11 | Re: Overflow hazard in pgbench |
| Previous Message | Michael Paquier | 2021-06-28 07:53:28 | Re: Different compression methods for FPI |