In Postgres, Index FILLFACTOR only works for monotonically increasing
column values and for random values it will do 50:50 block split. However
it's really less likely that monotonically increasing columns gets updated
then why we need to waste that 10% space and also making Index range scan
on suc
Why Postgres default FILLFACTOR for table is 100 and for Index is 90.
Although Oracle is having completely different MVCC architecture, it uses
default 90 for table and 100 for Index (exact reverse of Postgres)
Postgres blocks needed more spaces for row update compares to Oracle
(because Oracle k
