Re: Vacuuming the free space map considered harmful?

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Vacuuming the free space map considered harmful?
Date: 2025-03-19 14:06:49
Message-ID: ABF82A2D-814E-4533-9551-ED99A40E1CA1@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Mar 19, 2025, at 12:12, Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> Assuming this analysis is correct, I agree that the FSM vacuuming should
> also be throttled, as long as that can be done without blocking
> concurrent operations (insertions) on the table.

From an (admittedly somewhat naïve) look at the code, it appears that having it honor the cost delay wouldn't introduce excessive blocking, as long as the delay wasn't implemented at a really dumb place.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2025-03-19 14:06:58 Re: PATCH: warn about, and deprecate, clear text passwords
Previous Message Christophe Pettus 2025-03-19 14:05:47 Re: Vacuuming the free space map considered harmful?