Re: Write visibility map during CLUSTER/VACUUM FULL

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, 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: 2019-11-29 02:32:15
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Fri, Sep 20, 2019 at 01:05:06PM -0700, Andres Freund wrote:
> I don't think we should have yet another copy of logic determining
> visibility. It has repeatedly proven hard to get right in the past, and
> it'll not get better by having yet another copy. Especially not because
> we've basically already done a HTSV (via
> heapam_relation_copy_for_cluster), and we're now redoing a poor man's
> version of it.

These comments are unanswered for more than 2 months, so I am marking
this entry as returned with feedback. Please feel free to change if
you think that's not adapted.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2019-11-29 02:39:48 Re: PATCH: standby crashed when replay block which truncated in standby but failed to truncate in master node
Previous Message Michael Paquier 2019-11-29 02:29:03 Re: [PATCH] ltree, lquery, and ltxtquery binary protocol support