TOAST - why separate visibility map

From: Virender Singla <virender(dot)cse(at)gmail(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: TOAST - why separate visibility map
Date: 2021-11-19 18:45:40
Message-ID: CAM6Zo8yobnCXFfmydfY+_nmzjdbN_rUHiL9WBGcGTS2ZSGUS7A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2021-11-19 19:02:37 Re: update with no changes
Previous Message Tomas Vondra 2021-11-19 18:37:05 Re: sequence cache is kept forever