Re: vacuum -vs reltuples on insert only index

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: vacuum -vs reltuples on insert only index
Date: 2020-11-02 20:19:58
Message-ID: CAH2-WzmJ3MGJHeW+pNgNbpEcY_cv0+RyYhfu=LHAX=Y+fCxDCQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Just one more postscript...

On Mon, Nov 2, 2020 at 12:06 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> Just to be clear: I am not proposing that we set
> 'IndexBulkDeleteResult.estimated_count = false' here

I meant 'IndexBulkDeleteResult.estimated_count = true'. So my patch
doesn't touch that field at all.

> In other words, I think that the remaining posting-list related
> inaccuracies are comparable to the existing inaccuracies caused by
> concurrent page splits during nbtree vacuuming (I describe the problem
> right next to an old comment about that issue, in fact).

I meant the inaccuracies that remain *once my patch is committed*.
(Clearly the current behavior of setting pg_class.reltuples to zero
during cleanup-only vacuuming is a bug.)

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2020-11-02 20:43:14 Re: Collation versioning
Previous Message Peter Geoghegan 2020-11-02 20:06:17 Re: vacuum -vs reltuples on insert only index