Re: Partial index "microvacuum" - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Partial index "microvacuum"
Date
Msg-id CAH2-Wz=n59hMLB4QozO+=DQg7GCDTjDo=03NBMYAFbNAQinGFw@mail.gmail.com
Whole thread Raw
In response to Partial index "microvacuum"  (Marko Tiikkaja <marko@joh.to>)
Responses Re: Partial index "microvacuum"  (Marko Tiikkaja <marko@joh.to>)
List pgsql-hackers
On Wed, Sep 15, 2021 at 7:18 AM Marko Tiikkaja <marko@joh.to> wrote:
> So I've been looking at issues we used to have in production some time
> ago which eventually lead us to migrating away from partial indexes in
> some cases.  In the end, I'm surprised how easy this (or at least a
> similar case) was to reproduce.

> (I've tested this on 9.6, v11 and v13.  13 seems to be a bit better
> here, but not "fixed", I think.)

What about v14? There were significant changes to the
microvacuum/index deletion stuff in that release:

https://www.postgresql.org/docs/14/btree-implementation.html#BTREE-DELETION

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Ranier Vilela
Date:
Subject: Re: Getting ERROR "subplan "SubPlan 1" was not initialized" in EXISTS subplan when using for list partition.
Next
From: Tom Lane
Date:
Subject: Re: Hook for extensible parsing.