Skip to content
Snippets Groups Projects

set fillfactor for tables where many records are frequently updated

Merged Marcin requested to merge mi_speedup_updates_hive_posts_after_sync into develop

Changed the fillfactor from default of 100% to 70% to reserve additional space on data pages for subsequent copies of updated records. This prevents postgresql from always adding a new row version to the last (active) page and thereby creating data fragmentation, which causes slow queries. When the table is badly fragmented, we have seen execution time differences starting from 20s up to 130s.

Edited by Dan Notestein

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • merged

  • Bartek Wrona mentioned in commit e2339015

    mentioned in commit e2339015

  • Dan Notestein changed title from set fillfactor for tables intesively updated to set fillfactor for tables that are updated frequently

    changed title from set fillfactor for tables intesively updated to set fillfactor for tables that are updated frequently

  • Dan Notestein changed title from set fillfactor for tables that are updated frequently to set fillfactor for tables where many records are frequently updated

    changed title from set fillfactor for tables that are updated frequently to set fillfactor for tables where many records are frequently updated

  • Dan Notestein changed the description

    changed the description

Please register or sign in to reply
Loading