> > I have an index on a timestamp value that is inserted, for 90% > > of the inserts, in increasing order. No updates, no deletes on the > > table (appends only). > > The bit about "increasing order" is a red herring here. If you have > no updates, then you can leave the FILLFACTOR alone. > > FILLFACTOR controls how much extra room there is in the way the table > is stored, so that if a row is UPDATEd it might be possible to store > the row in the same disk page. This alleviates certain pathological > conditions with high-UPDATE tables and the way Postgres stores the > data (the non-overwriting storage manager). (please add the list when replying to emails) I'm talking about the index fillfactor, not the table fillfactor... -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
