From: | Virender Singla <virender(dot)cse(at)gmail(dot)com> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: TOAST - why separate visibility map |
Date: | 2021-11-19 19:48:58 |
Message-ID: | CAM6Zo8zUq2s1d=T6N=Ou+0-Ex3mxVdGZLoc9B61Pmk50fDjAqw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Another point that currently manual VACUUM job does cleanup/freeze on
primary table first and then toast table. It looks easy pick to possibly
have a configurable parameter to run it on both the tables in parallel.
On Sat, Nov 20, 2021 at 12:15 AM Virender Singla <virender(dot)cse(at)gmail(dot)com>
wrote:
> Why do Toast tables have it's own visibility map and xmin, xmax columns
> etc?
> Isn't it increasing row size in a toast table and adding more complexity?
>
> Ideally all the vacuum cleanup on a TOAST can be done based on Primary
> table xmin,xmax and VM info. Yes, that makes any cleanup on TOAST to be
> glued up with the Primary table.
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2021-11-19 19:50:54 | Re: Why not try for a HOT update, even when PageIsFull()? |
Previous Message | Bossart, Nathan | 2021-11-19 19:22:35 | Re: archive modules |