| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Marko Tiikkaja <marko(at)joh(dot)to> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Partial index "microvacuum" |
| Date: | 2021-09-15 16:25:33 |
| Message-ID: | CAH2-Wz=n59hMLB4QozO+=DQg7GCDTjDo=03NBMYAFbNAQinGFw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Sep 15, 2021 at 7:18 AM Marko Tiikkaja <marko(at)joh(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-09-15 16:57:00 | Re: Hook for extensible parsing. |
| Previous Message | Ranier Vilela | 2021-09-15 16:18:11 | Re: Getting ERROR "subplan "SubPlan 1" was not initialized" in EXISTS subplan when using for list partition. |