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

From Virender Singla
Subject TOAST - why separate visibility map
Date
Msg-id CAM6Zo8yobnCXFfmydfY+_nmzjdbN_rUHiL9WBGcGTS2ZSGUS7A@mail.gmail.com
Whole thread Raw
Responses Re: TOAST - why separate visibility map
Re: TOAST - why separate visibility map
List pgsql-hackers
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: Tomas Vondra
Date:
Subject: Re: sequence cache is kept forever
Next
From: "David G. Johnston"
Date:
Subject: Re: update with no changes