| From: | Marko Tiikkaja <marko(at)joh(dot)to> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Partial index "microvacuum" |
| Date: | 2021-09-16 11:45:06 |
| Message-ID: | CAL9smLC=SxYiN7yZ4HDyk0RnZyXoP2vaHD-Vg1JskOEHyhMXug@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Sep 15, 2021 at 7:25 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> 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
Huh. Interesting. I'm sorry, I wasn't aware of this work and didn't
have version 14 at hand. But it looks like both the partial index as
well as the secondary index on (id::text) get cleaned up nicely there.
I even tried a version where I have a snapshot open for the entire
run, and the subsequents SELECTs clean the bloat up. I'll need to
read up on the details a bit to understand exactly what changed, but
it appears that at least this particular pattern has already been
fixed.
Thank you so much for your work on this!
.m
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2021-09-16 12:36:26 | Re: Logical replication keepalive flood |
| Previous Message | Ranier Vilela | 2021-09-16 11:03:23 | Re: Signed vs Unsigned (take 2) (src/backend/storage/ipc/procarray.c) |