From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
---|---|
To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
Cc: | PostgreSQL-Dev <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] [PATCH] Vacuum: Update FSM more frequently |
Date: | 2018-02-27 15:54:04 |
Message-ID: | CAGTBQpYEj2LTQYuecvmYY=G_FSnioEdBzHNaYQWG6_z=nLEB0A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Feb 6, 2018 at 4:56 AM, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
> For vacuuming fsm of index, we might have to consider to
> vacuum fsm of index after lazy_vacuum_index.
I've been thinking about that, and I think you're right.
So here's a fourth patch that adds that to nbtree's bulkdelete implementation.
Seems to be the best place to add such a thing.
GIN and GIST don't delete pages until vacuumcleanup, so they can't do
the same, sadly.
Attachment | Content-Type | Size |
---|---|---|
0004-Index-vacuum-Vacuum-FSM-after-each-bulkdelete-call.patch | text/x-patch | 3.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2018-02-27 16:05:14 | Re: [HACKERS] path toward faster partition pruning |
Previous Message | Robert Haas | 2018-02-27 15:36:01 | Re: atomics.h may not be included from frontend code |