Re: Something is wrong with wal_compression

Justin Pryzby <pryzby@telsasoft.com>

From: Justin Pryzby <pryzby@telsasoft.com>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: pgsql-hackers@lists.postgresql.org, Michael Paquier <michael@paquier.xyz>

Date: 2023-01-26T20:08:27Z

Lists: pgsql-hackers

On Thu, Jan 26, 2023 at 02:43:29PM -0500, Tom Lane wrote:
> The symptom being exhibited by Michael's new BF animal tanager
> is perfectly reproducible elsewhere.

I think these tests have always failed with wal_compression ?

https://www.postgresql.org/message-id/20210308.173242.463790587797836129.horikyota.ntt%40gmail.com
https://www.postgresql.org/message-id/20210313012820.GJ29463@telsasoft.com
https://www.postgresql.org/message-id/20220222231948.GJ9008@telsasoft.com

https://www.postgresql.org/message-id/YNqWd2GSMrnqWIfx@paquier.xyz
|My buildfarm machine has been changed to use wal_compression = lz4,
|while on it for HEAD runs.

Commits

Remove recovery test 011_crash_recovery.pl
- 403d82dd54b5 11.19 landed
- e8fb2a721b36 12.14 landed
- ee11824ac4c2 13.10 landed
- 96d42bd27fef 14.7 landed
- c5b2975ec183 15.2 landed
- 8c1cd726c5d9 16.0 landed
Add a txid_status function.
- 857ee8e391ff 10.0 cited