Re: lazy_scan_heap() should release lock on buffer before vacuuming FSM

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Melanie Plageman <melanieplageman(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: lazy_scan_heap() should release lock on buffer before vacuuming FSM
Date: 2023-11-15 21:32:48
Message-ID: CA+TgmoYfQwaQ6dUD0z-s=n5UHU2OWX_4uAxVQ0aCMvWwbf6cuQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 13, 2023 at 8:26 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> I think this undersells the situation a bit. We right now do
> FreeSpaceMapVacuumRange() for 8GB of data (VACUUM_FSM_EVERY_PAGES) in the main
> fork, while holding an exclusive page level lock.

That sounds fairly horrific?

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2023-11-15 21:48:53 Re: Popcount optimization using AVX512
Previous Message Melanie Plageman 2023-11-15 21:21:45 Re: lazy_scan_heap() should release lock on buffer before vacuuming FSM