From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Alexander Shchapov <alexanderad(at)gmail(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Detailed progress reporting for "vacuuming indexes" stage |
Date: | 2017-01-25 01:37:59 |
Message-ID: | CAB7nPqS1YbxRDzNwR3N0XCAPMWeeLmQJ1S6Pk4JovNDdV+fMNQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Jan 24, 2017 at 5:37 PM, Alexander Shchapov
<alexanderad(at)gmail(dot)com> wrote:
> On Tue, Jan 24, 2017 at 8:57 AM, Michael Paquier
> <michael(dot)paquier(at)gmail(dot)com> wrote:
>> What would be more interesting would be like the heap to get
>> information on the index block being cleaned up with reports being
>> done via index_bulk_delete(). That's more work, and that would be more
>> helpful than just a number.
>>
>> So patches welcome.
>
> Thanks for the reply and a tip, Michael.
> Do I get it correctly, that you suggesting to calculate something like
> index_blks_total and increment index_blks_vacuumed?
Something like that may be helpful as vacuum is basically triggering a
bulk deletion on the indexes vacuumed. What makes the thing tricky is
how to integrate that correctly with index AMs. So while it can be
done, it deserves careful thoughts.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Shailesh Singh | 2017-01-25 05:28:29 | I could not see any row in audit table |
Previous Message | Andy Colson | 2017-01-25 01:12:37 | Re: What is the purpose of PostGIS on PostgreSQL? |