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. >
