From: | Ranjith Paliyath <ranjithp(at)suntecgroup(dot)com> |
---|---|
To: | Ron <ronljohnsonjr(at)gmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Purging few months old data and vacuuming in production |
Date: | 2023-01-06 08:44:18 |
Message-ID: | SEZPR06MB56905EB1343165E6D1C8B5B4C2FB9@SEZPR06MB5690.apcprd06.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thank you for the details, experience shared and the suggestions.
Apologies for the delay in collecting the response for the queries.
(1)Are the tables tied together by FK?
- Overall there are 9 tables (sorry not 6 as mentioned originally) that are being purged. Only 4 tables would be having FK relationship.
(2)How big are the rows?
- The 9 tables now occupy almost 2TB space. Below is the rowsize (in bytes) and record-count details -
236 188,055,675
297 296,941,261
371 58,673,649
95 57,477,553
904 296,743,680
234 188,161,891
414 430,411,653
707 735,895,015
128 155,104,922
(3)Is there an index on the date field?
- Yes. But only in one table, which is the main table (records to purge in rest of the tables is based on this table).
(4)Can you drop unneeded indices during the window, and then rebuild them afterward?
- Not sure, if the time window within which the purge process must complete would be sufficient to do drop and rebuild of indices.
(5)How beefy is your hardware?
- No. of cores - 64
Memory - 128GB
Disk - SSD, Total capacity - 8.5TB
Thank you...This electronic mail (including any attachment thereto) may be confidential and privileged and is intended only for the individual or entity named above. Any unauthorized use, printing, copying, disclosure or dissemination of this communication may be subject to legal restriction or sanction. Accordingly, if you are not the intended recipient, please notify the sender by replying to this email immediately and delete this email (and any attachment thereto) from your computer system...Thank You.
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2023-01-06 10:21:26 | Re: best practice to patch a postgresql version? |
Previous Message | Laurenz Albe | 2023-01-06 05:43:22 | Re: best practice to patch a postgresql version? |