| From: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
|---|---|
| To: | "Karthik Jagadish (kjagadis)" <kjagadis(at)cisco(dot)com> |
| Cc: | Amul Sul <sulamul(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "Prasanna Satyanarayanan (prassaty)" <prassaty(at)cisco(dot)com>, "Chandruganth Ayyavoo Selvam (chaayyav)" <chaayyav(at)cisco(dot)com>, "Jaganbabu M (jmunusam)" <jmunusam(at)cisco(dot)com> |
| Subject: | Re: Tables not getting vacuumed in postgres |
| Date: | 2022-11-08 14:24:13 |
| Message-ID: | C1D1789E-7586-4062-B119-ECE3C4C29D5B@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Nov 8, 2022, at 5:21 AM, Karthik Jagadish (kjagadis) <kjagadis(at)cisco(dot)com> wrote:
>
> I didn’t get your point dead tuples are visible to transaction means? Vacuuming job is to remove dead tuples right?
Please see https://www.2ndquadrant.com/en/blog/when-autovacuum-does-not-vacuum/ for more information about your question. Specifically, you might look at the third section down, "Long transactions", which starts with "So, if the table is vacuumed regularly, surely it can’t accumulate a lot of dead rows, right?" You might benefit from reading the entire article rather than skipping down to that section.
I hope it helps....
—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Christensen | 2022-11-08 16:17:56 | Re: [PATCHES] Post-special page storage TDE support |
| Previous Message | Masahiko Sawada | 2022-11-08 14:14:39 | Re: [PoC] Improve dead tuple storage for lazy vacuum |