Re: Write visibility map during CLUSTER/VACUUM FULL

From: Anna Akenteva <a(dot)akenteva(at)postgrespro(dot)ru>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Write visibility map during CLUSTER/VACUUM FULL
Date: 2021-06-28 08:22:01
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 2019-11-29 05:32, Michael Paquier wrote:
> These comments are unanswered for more than 2 months, so I am marking
> this entry as returned with feedback.

I'd like to revive this patch. To make further work easier, attaching a
rebased version of the latest patch by Alexander.

As for having yet another copy of logic determining visibility: the
visibility check was mainly taken from heap_page_is_all_visible(), so I
refactored the code to make sure that logic is not duplicated. The
updated patch is attached too.

Anna Akenteva
Postgres Professional:
The Russian Postgres Company

Attachment Content-Type Size
0001-write-vm-during-cluster-3-rebase.patch text/x-diff 9.5 KB
0001-write-vm-during-cluster-4.patch text/x-diff 19.0 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2021-06-28 08:39:44 Re: Fix for segfault in logical replication on master
Previous Message Fabien COELHO 2021-06-28 08:20:52 Re: Preventing abort() and exit() calls in libpq