storage-fsm.md 1.2 KB
Newer Older
K
KyleZhang 已提交
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
## 70.3. Free Space Map

[]()[]()

Each heap and index relation, except for hash indexes, has a Free Space Map
(FSM) to keep track of available space in the relation. It's stored
alongside the main relation data in a separate relation fork, named after the
filenode number of the relation, plus a `_fsm` suffix. For example,
if the filenode of a relation is 12345, the FSM is stored in a file called`12345_fsm`, in the same directory as the main relation file.

The Free Space Map is organized as a tree of FSM pages. The
bottom level FSM pages store the free space available on each
heap (or index) page, using one byte to represent each such page. The upper
levels aggregate information from the lower levels.

Within each FSM page is a binary tree, stored in an array with
one byte per node. Each leaf node represents a heap page, or a lower levelFSM page. In each non-leaf node, the higher of its children's
values is stored. The maximum value in the leaf nodes is therefore stored
at the root.

See `src/backend/storage/freespace/README` for more details on
how the FSM is structured, and how it's updated and searched.
The [pg\_freespacemap](pgfreespacemap.html) module
can be used to examine the information stored in free space maps.