Hello, >I think it'd be better to combine both numbers into one report: >It'd also be good to standardize on where the * 100 is happening. Done >can be replaced by >(itemptr->ipblkid != vacrelstats->last_scanned_page) Get compiler error : invalid operands to binary != (have ‘BlockIdData’ and ‘BlockIdData’) >vacrelstats->current_index_scanned_page_count++; Done Please find v3 attached.
I am struggling to create maintenance work memory exhaustion. Did the following maintenance_work_mem=1MB. Inserted 10 million records in tbl1 with 3 indexes. Deleted 5 million and vacuumed. So far no error. I could keep bumping up the records to say 100 million and try to get this error. This seems a tedious manner to simulate maintenance work memory exhaustion. Is there a better way? To insert I am using COPY (from a csv which has 10 million records) and building indexes after insert is complete. Thank you Sameer ______________________________________________________________________ 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.
IndexScanProgress_v3.patch
Description: IndexScanProgress_v3.patch
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
