Hi,

On Thu, 6 Aug 2026 at 07:22, Yuefei Shi <[email protected]> wrote:

> Reviewed this patch.
>
> The issue seems valid. PostgreSQL-generated manifests should not normally
> contain such LSNs, but a malformed or modified manifest could make the
> parser operate on a different LSN than the one specified. The current
> sscanf() based parser allows this through truncation of oversized
> components and ignored trailing characters.
>
> The proposed fix looks good and the tests cover the regression cases.
>
Thanks for the review!

Attaching v2 which uses the new pg_parse_lsn funct.

Regards,
Ayush

Attachment: v2-0001-Reject-out-of-range-LSNs-in-backup-manifests.patch
Description: Binary data

Reply via email to