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 should be getting many passes through the >indexes. >Studying the output of VACUUM VERBOSE will confirm that (or just >throw a 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 times while vacuuming after 5 million records deleted. Figuring out number of multiple index passes beforehand, accurately, is the problem to solve. Clearly need to study this some 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.tha...@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. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
