Re: Adding REPACK [concurrently] - Mailing list pgsql-hackers

From Marcos Pegoraro
Subject Re: Adding REPACK [concurrently]
Date
Msg-id CAB-JLwbvqNnTmgZsE3T-KbAOO5w04uwdeYfSVtdumPfdSG6NJQ@mail.gmail.com
Whole thread Raw
In response to Re: Adding REPACK [concurrently]  (Álvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
Em qui., 4 de dez. de 2025 às 12:43, Álvaro Herrera <alvherre@alvh.no-ip.org> escreveu:
If you only have a small number of pages that have this problem, then
you don't actually need to do anything -- the pages will be marked free
by regular vacuuming, and future inserts or updates can make use of
those pages.  It's not a problem to have a small number of pages in
empty state for some time.

So if you're trying to do this, the number of problematic pages must be
large.

Not necessarily. I have some tables where I like to use CLUSTER 
every 2 or 3 months, to reorganize the data based on an index 
and consequently load fewer pages with each call. These tables 
don't have more than 2 or 3% of dead records, but they are quite 
disorganized from the point of view of that index, since the 
inserted and updated records don't follow the order I determined.


regards
Marcos

pgsql-hackers by date:

Previous
From: Álvaro Herrera
Date:
Subject: Re: bt_index_parent_check and concurrently build indexes
Next
From: Andres Freund
Date:
Subject: Re: headerscheck ccache support