Re: Fix comments of heap_prune_chain()

From: Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>
To: ikedamsh(at)oss(dot)nttdata(dot)com
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Fix comments of heap_prune_chain()
Date: 2021-07-12 20:57:15
Message-ID: CAEze2Wh5Ybutw78e48j-YuUiMGeL3U8C+=0OjVmsK7mu2GEXaw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 12 Jul 2021 at 13:14, <ikedamsh(at)oss(dot)nttdata(dot)com> wrote:
>
> Hi,
>
> While I’m reading source codes related to vacuum, I found comments which
> don’t seem to fit the reality. I think the commit[1] just forgot to fix
them.
> What do you think?

Hmm, yes, those are indeed some leftovers.

Some comments on the suggested changes:

- * caused by HeapTupleSatisfiesVacuum. We just add entries to the arrays
in
+ * caused by heap_prune_satisfies_vacuum. We just add entries to the
arrays in

I think that HeapTupleSatisfiesVacuumHorizon might be an alternative
correct replacement here.

- elog(ERROR, "unexpected HeapTupleSatisfiesVacuum result");
+ elog(ERROR, "unexpected heap_prune_satisfies_vacuum
result");

The type of the value is HTSV_Result; where HTSV stands for
HeapTupleSatisfiesVacuum, so if we were to replace this, I'd go for
"unexpected result from heap_prune_satisfies_vacuum" as a message instead.

Kind regards,

Matthias van de Meent

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2021-07-12 21:00:05 Re: [PATCH] Don't block HOT update by BRIN index
Previous Message Alvaro Herrera 2021-07-12 20:55:31 Re: [PATCH] Don't block HOT update by BRIN index