Re: [BUG] [PATCH] pg_basebackup produces wrong incremental files after relation truncation in segmented tables

From: Oleg Tkachenko <oatkachenko(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Amul Sul <sulamul(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Stanislav Bashkyrtsev <stanislav(dot)bashkyrtsev(at)elsci(dot)io>
Subject: Re: [BUG] [PATCH] pg_basebackup produces wrong incremental files after relation truncation in segmented tables
Date: 2026-01-16 12:10:27
Message-ID: 1E2326C0-185A-4D91-867C-18BF94D186DD@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi, Robert

As you suggested, I've updated the test so that it produces small files consistently across platforms.
On one specific platform (with segment size = 6 blocks), it still exercises the relevant code path.
And I've also applied the style changes you mentioned.

Best regards,
Oleg

Attachment Content-Type Size
0001-Clamp-truncation_block_length-to-RELSEG_SIZE-when-se.patch application/octet-stream 8.1 KB
unknown_filename text/plain 3.0 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrey Borodin 2026-01-16 12:13:36 Re: CREATE TABLE LIKE INCLUDING TRIGGERS
Previous Message Andres Freund 2026-01-16 12:02:46 Re: Buffer locking is special (hints, checksums, AIO writes)