> On Mar 29, 2021, at 1:06 PM, Robert Haas <robertmh...@gmail.com> wrote:
> 
> Hmm, so this got ~10x bigger from my version. Could you perhaps
> separate it out into a series of patches for easier review? Say, one
> that just fixes the visibility logic, and then a second to avoid doing
> the TOAST check with a buffer lock held, and then more than that if
> there are other pieces that make sense to separate out?

Sure, here are four patches which do the same as the single v12 patch did.


Attachment: v13-0001-Refactoring-function-check_tuple_header_and_visi.patch
Description: Binary data

Attachment: v13-0002-Replacing-implementation-of-check_tuple_visibili.patch
Description: Binary data

Attachment: v13-0003-Renaming-report_corruption-as-report_main_corrup.patch
Description: Binary data

Attachment: v13-0004-Checking-toast-separately-from-the-main-table.patch
Description: Binary data

—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



Reply via email to