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

From Tom Lane
Subject Re: TOAST - why separate visibility map
Date
Msg-id 3172107.1637424982@sss.pgh.pa.us
Whole thread Raw
In response to Re: TOAST - why separate visibility map  (Andres Freund <andres@anarazel.de>)
Responses Re: TOAST - why separate visibility map
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> On November 19, 2021 12:31:00 PM PST, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> It might be feasible to drop the visibility map for toast tables, though.

> I think it be a bad idea - the VM is used by vacuum to avoid rereading already vacuumed ranges. Loosing that for
largetoast tables would be bad. 

Ah, right.  I was thinking vacuuming depended on the other map fork,
but of course it needs this one.

In short, there are indeed good reasons why it works like this.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Test::More version
Next
From: Hans Buschmann
Date:
Subject: AW: VS2022: Support Visual Studio 2022 on Windows