Re: [PROPOSAL] VACUUM Progress Checker.

Поиск
Список
Период
Сортировка
От Thakur, Sameer
Тема Re: [PROPOSAL] VACUUM Progress Checker.
Дата
Msg-id FB70B48CE8A70B4C8D050211EC78690F7911C9BF@MAIL703.KDS.KEANE.COM
обсуждение исходный текст
Ответ на Re: [PROPOSAL] VACUUM Progress Checker.  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Список pgsql-hackers
Hello,
>Yes. Any percent completion calculation will have to account for the case of needing multiple passes through all the
indexes.

>Each dead tuple requires 6 bytes (IIRC) of maintenance work mem. So if you're deleting 5M rows with m_w_m=1MB you
shouldbe getting many passes through the indexes. >Studying the output of VACUUM VERBOSE will confirm that (or just
throwa temporary WARNING in the path where we start the scan). 

Yes I see the problem now. I get the message "WARNING:  Overall index percentage completion 100.000000" logged > 25
timeswhile vacuuming after 5 million records deleted. 
Figuring out number  of multiple index passes beforehand, accurately, is the problem to solve. Clearly need to study
thissome more. 
Thank you,
Sameer Thakur | Senior Software Specialist | NTTDATA Global Delivery Services Private Ltd | w. +91.20.6641.7146 | VoIP:
8834.8146| m. +91 989.016.6656 | sameer.thakur@nttdata.com | Follow us on Twitter@NTTDATAAmericas 


______________________________________________________________________
Disclaimer: This email and any attachments are sent in strictest confidence
for the sole use of the addressee and may contain legally privileged,
confidential, and proprietary data. If you are not the intended recipient,
please advise the sender by replying promptly to this email and then delete
and destroy this email and any attachments without any further use, copying
or forwarding.

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Kouhei Kaigai
Дата:
Сообщение: Re: Asynchronous execution on FDW
Следующее
От: Petr Jelinek
Дата:
Сообщение: Re: TABLESAMPLE patch is really in pretty sad shape