Synthetic keys and index fillfactor

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Synthetic keys and index fillfactor
Date: 2023-01-12 22:45:05
Message-ID: d50cc687-d903-3312-cee2-4f4fdc864b0a@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin


(This mostly pertains to recreating a PK on an existing table.)

Is there any reason to have the PK index on an ever-increasing field (for
example SERIAL, sequence or timestamp fed by clock_timestamp() at time zone
'UTC') be anything but fillfactor=100?

New records will always be added to the "lower right hand corner" of the
tree, so having 20% empty space in the rest of the tree would just waste
space (mainly buffers, but disk space could even start to add up on Very Big
Tables).

--
Born in Arizona, moved to Babylonia.

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message David G. Johnston 2023-01-12 22:54:38 Re: Synthetic keys and index fillfactor
Previous Message JP Pozzi 2023-01-12 18:09:27 Re: MSSQL to PostgreSQL Migration