Documentation / Storage Parameters / Tables and materialized views
fillfactor
Tables and materialized views fillfactor
The fillfactor for a table is a percentage between 10 and 100. 100 (complete packing) is the default. When a smaller fillfactor is specified, INSERT operations pack table pages only to the indicated percentage; the remaining space on each page is reserved for updating rows on that page. This gives UPDATE a chance to place the updated copy of a row on the same page as the original, which is more efficient than placing it on a different page, and makes heap-only tuple updates more likely. For a table whose entries are never updated, complete packing is the best choice, but in heavily updated tables smaller fillfactors are appropriate. This parameter cannot be set for TOAST tables.
Reading PostgreSQL 18.6.
Description
The fillfactor for a table is a percentage between 10 and 100. 100 (complete packing) is the default. When a smaller fillfactor is specified, INSERT operations pack table pages only to the indicated percentage; the remaining space on each page is reserved for updating rows on that page. This gives UPDATE a chance to place the updated copy of a row on the same page as the original, which is more efficient than placing it on a different page, and makes heap-only tuple updates more likely. For a table whose entries are never updated, complete packing is the best choice, but in heavily updated tables smaller fillfactors are appropriate. This parameter cannot be set for TOAST tables.
- Applies to
- Tables and materialized views
- Value type
- integer
- Default
- 100
- Range
- 10–100 percent
Usage
WITH (fillfactor = value)Scope
This relation-level setting applies to the table or materialized view. Any corresponding global parameter has a separate entry.
Common table storage rules
The WITH clause can specify storage parameters for tables, and for indexes associated with a UNIQUE , PRIMARY KEY , or EXCLUDE constraint. Storage parameters for indexes are documented in CREATE INDEX . The storage parameters currently available for tables are listed below. For many of these parameters, as shown, there is an additional parameter with the same name prefixed with toast. , which controls the behavior of the table's secondary TOAST table, if any (see Section 66.2 for more information about TOAST). If a table parameter value is set and the equivalent toast. parameter is not, the TOAST table will use the table's parameter value. Specifying these parameters for partitioned tables is not supported, but you may specify them for individual leaf partitions.
Materialized views
This clause specifies optional storage parameters for the new materialized view; see Storage Parameters in the CREATE TABLE documentation for more information. All parameters supported for CREATE TABLE are also supported for CREATE MATERIALIZED VIEW . See CREATE TABLE for more information.
Related entries
Documentation and source
Source build
- Version
- 18.6
- Build
- Local English manual 18.6
- Source fingerprint
eb6c2292fdf28e1b4635ab478eec3919411cdf4a6c07553387870e26201f3744
Related entries
autovacuum_analyze_scale_factorautovacuum_analyze_scale_factorautovacuum_analyze_thresholdautovacuum_analyze_thresholdautovacuum_enabledautovacuum_enabledautovacuum_freeze_max_ageautovacuum_freeze_max_ageautovacuum_freeze_min_ageautovacuum_freeze_min_ageautovacuum_freeze_table_ageautovacuum_freeze_table_ageautovacuum_multixact_freeze_max_ageautovacuum_multixact_freeze_max_ageautovacuum_multixact_freeze_min_ageautovacuum_multixact_freeze_min_ageautovacuum_multixact_freeze_table_ageautovacuum_multixact_freeze_table_ageautovacuum_vacuum_cost_delayautovacuum_vacuum_cost_delayautovacuum_vacuum_cost_limitautovacuum_vacuum_cost_limitautovacuum_vacuum_insert_scale_factorautovacuum_vacuum_insert_scale_factor
Back to Storage Parameters · Recorded in PostgreSQL 10 through 20; the first sample is not necessarily its introduction.