Hi,Here is a refactored test.Now, it creates data depending on the relation block size, so it works even if the segment size is not standard. I tested it locally with segment_size_blocks = 6, and it works correctly.I would be happy to hear your comments or suggestions.Regards,Oleg
0001-Clamp-trunc
-correctness-of-the-truncation_block_length-.patch
Description: Binary data
On Dec 15, 2025, at 21:13, Robert Haas wrote:On Mon, Dec 15, 2025 at 1:46 PM Oleg Tkachenko wrote:Also, I’ve attached a patch based on your guidance. The changes are effectively the same as your suggested approach, but I would be
included in incremental backups.I’ve tested the version with the limit enforced to RELSEG_SIZE, and it works correctly.Also, I’ve attached a patch based on your guidance. The changes are effectively the same as your suggested approach, but I would be happy to be listed as a contributor.Regards,Oleg
revise it if needed.Best regards,Oleg Tkachenko<>
On Nov 14, 2025, at 20:43, Oleg Tkachenko wrote:Hello PostgreSQL developers,I’ve encountered a bug in the incremental backup feature that prevents restoration of backups containing relations larger than 1 GB that were vacuum-truncated.P
up.Attempt to restore using pg_combinebackup.Observe the truncation block length error.PatchA patch correcting this logic is attached, and I’m happy to provide additional details or revisions if helpful.Best regards,Oleg Tkachenko
bug_truncation_block_length.patch
Description: Binary data
