Re: Plug-in coverage hole for pglz_decompress()

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

To: Ayush Tiwari <ayushtiwari.slg01@gmail.com>

Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>, Andrew Dunstan <andrew@dunslane.net>

Date: 2026-05-13T06:19:30Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Add more tests for corrupted data with pglz_decompress()
- 5c00f4e2e3bc 14 (unreleased) landed
- f4ba78081895 15 (unreleased) landed
- 5f12d86dd762 16 (unreleased) landed
- 54eeefaedbee 17 (unreleased) landed
- 89192080f0a9 18 (unreleased) landed
- 900c07b854a7 19 (unreleased) landed

On Mon, May 11, 2026 at 12:27:43PM +0530, Ayush Tiwari wrote:
> The two added inputs seem to cover the intended cases: one produces an
> offset larger than the amount of output already written, and the other
> produces offset zero, so both exercise the corrupt-input guard in
> pglz_decompress().

Thanks for double-checking.  Done.
--
Michael