From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | Alexander Shchapov <alexanderad(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Detailed progress reporting for "vacuuming indexes" stage |
Date: | 2017-01-24 09:08:01 |
Message-ID: | CANP8+j+DKzAZs17OPNs6Q+1Q9VPhhdC6uNpAcvC7iSaLd--O_A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 24 January 2017 at 06:57, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> wrote:
> On Mon, Jan 23, 2017 at 8:32 PM, Alexander Shchapov
> <alexanderad(at)gmail(dot)com> wrote:
>> There are 7 stages for standard VACUUM process which is reportable via
>> this view. For time consuming stages like "scanning heap" or
>> "vacuuming heap" you are able to get stage progress idea by doing:
>>
>> (heap_blks_scanned | heap_blks_vacuumed) / heap_blks_total * 100%
>>
>> However stage "vacuuming indexes" does not give any idea of how long
>> this stage might take. We have some rather big (500M+ records) with
>> 5-7 indexes. Sometimes it takes us 20 hours+ to get table vacuumed and
>> all progress reporting we have for stage 3 is that it is stage 3.
>
> Yes, things could be improved here.
Yes, it seems that VACUUM progress reporting feature is only about 40% complete.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Torsten Förtsch | 2017-01-24 09:53:55 | change type from NUMERIC(14,4) to NUMERIC(24,12) |
Previous Message | Alexander Shchapov | 2017-01-24 08:37:14 | Re: Detailed progress reporting for "vacuuming indexes" stage |