Re: TOAST - why separate visibility map - Mailing list pgsql-hackers

From Virender Singla
Subject Re: TOAST - why separate visibility map
Date
Msg-id CAM6Zo8zUq2s1d=T6N=Ou+0-Ex3mxVdGZLoc9B61Pmk50fDjAqw@mail.gmail.com
Whole thread Raw
In response to TOAST - why separate visibility map  (Virender Singla <virender.cse@gmail.com>)
List 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.cse@gmail.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.


pgsql-hackers by date:

Previous
From: "Bossart, Nathan"
Date:
Subject: Re: archive modules
Next
From: Alvaro Herrera
Date:
Subject: Re: Why not try for a HOT update, even when PageIsFull()?