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:13:03
Message-ID: 9D682498-8481-4D47-A3D3-46F21491A9F8@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Mar 19, 2025, at 15:06, Christophe Pettus <xof(at)thebuild(dot)com> wrote:
>
> 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.

Specifically, it looks like doing the cost-based wait immediately after backend/storage/freespace/freespace.c:898 (in HEAD) wouldn't be in a critical section, although I could be totally in the weeds on this.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2025-03-19 14:38:13 Re: making EXPLAIN extensible
Previous Message Andres Freund 2025-03-19 14:12:27 Re: Vacuuming the free space map considered harmful?