Re: doc: explain pgstatindex fragmentation

Peter Eisentraut <peter@eisentraut.org>

From: Peter Eisentraut <peter@eisentraut.org>

To: Frédéric Yhuel <frederic.yhuel@dalibo.com>, Laurenz Albe <laurenz.albe@cybertec.at>, Bertrand Drouvot <bertranddrouvot.pg@gmail.com>

Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Benoit Lobréau <benoit.lobreau@dalibo.com>

Date: 2025-06-30T09:35:46Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

doc: explain pgstatindex fragmentation
- 960135114629 19 (unreleased) landed

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