Synthetic keys and index fillfactor

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




(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.





[Index of Archives]     [Postgresql Home]     [Postgresql General]     [Postgresql Performance]     [Postgresql PHP]     [Postgresql Jobs]     [PHP Users]     [PHP Databases]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Databases]     [Yosemite Forum]

  Powered by Linux