Re: doc: explain pgstatindex fragmentation

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Frédéric Yhuel <frederic(dot)yhuel(at)dalibo(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Benoit Lobréau <benoit(dot)lobreau(at)dalibo(dot)com>
Subject: Re: doc: explain pgstatindex fragmentation
Date: 2025-06-30 09:35:46
Message-ID: d755840a-7209-49d1-a2fa-94f0a0e5796d@eisentraut.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 24.01.25 15:41, Frédéric Yhuel wrote:
>
>
> On 1/24/25 14:58, Laurenz Albe wrote:
>> On Fri, 2025-01-24 at 13:34 +0000, Bertrand Drouvot wrote:
>>> + Since indexes have a default fillfactor of 90, this should be
>>> around 0.9 for
>>> + newly built indexes
>>>
>>> I think 0.9 should be replaced by 90 (that's the actual kind of
>>> output we'd get).
>>>
>
> Damn! I missed that one too...
>
>>> But having said that, I'm not sure we should mention those 90 stuff
>>> because it
>>> depends of the amount of data indexed (I mean if the index has a very
>>> few
>>> leaf pages, say < 5, then it's easy to be << 90 since it's an
>>> average). That's
>>> probably not the majority of indexes though so maybe just nuance the
>>> sentence a
>>> bit.
>>
>> Sorry about the 0.9.
>>
>> Perhaps the wording could be more careful: ... this should be around
>> 90 for
>> most newly built indexes of non-neglectable size.
>>
>
> It looks good to me (apart from the typo). v4 attached

committed

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2025-06-30 09:39:09 Re: tab complete for COPY populated materialized view TO
Previous Message Peter Eisentraut 2025-06-30 08:51:42 Re: Missing program_XXX calling in pgbench tests