Re: Vacuuming the free space map considered harmful?

From: Melanie Plageman <melanieplageman(at)gmail(dot)com>
To: Christophe Pettus <xof(at)thebuild(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Vacuuming the free space map considered harmful?
Date: 2025-03-19 13:12:36
Message-ID: CAAKRu_aXqoj2Vfqu3yzscsTX=2nPQ4y-aadCNz6nJP_o12GyxA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 19, 2025 at 4:54 AM Christophe Pettus <xof(at)thebuild(dot)com> wrote:
>
> Everything seems to point to the vacuum free space map operation, since it would have a lot of work to do in that particular situation, it happens at just the right place in the vacuum cycle, and its resource consumption is not throttled the way the regular vacuum operation is.

Do you know how big the FSM was?

As others have said, it could be worth adding a phase to
pg_stat_progress_vacuum.

I know you said you saw this all the way back to 15, but it made me
wonder if this would actually get worse after 17 and the tidstore
optimization -- since a large table with indexes requiring multiple
vacuum passes would actually end up having its FSM vacuumed sooner.

- Melanie

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message torikoshia 2025-03-19 13:15:32 Re: RFC: Allow EXPLAIN to Output Page Fault Information
Previous Message Andres Freund 2025-03-19 13:10:51 Re: Add -k/--link option to pg_combinebackup