Re: Plug-in coverage hole for pglz_decompress()

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>
Cc: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: Plug-in coverage hole for pglz_decompress()
Date: 2026-05-13 06:19:30
Message-ID: agQX8tDNRyIC4B71@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-05-13 06:22:29 Re: Fix unsafe PlannedStmt access in pg_stat_statements
Previous Message Peter Smith 2026-05-13 06:12:54 Re: Proposal: Conflict log history table for Logical Replication