Internals//Physical Storage: Database File Layout
  • References/Database/PostgreSQL/Internals/Physical Storage

This section describes the storage format at the level of files and directories. Traditionally, the configuration and data files used by a database

2025-01-10 15:47:30
Internals//Physical Storage: Visibility Map
  • References/Database/PostgreSQL/Internals/Physical Storage

Each heap relation has a Visibility Map (VM) to keep track of which pages contain only tuples that are known to be visible to all active transactions; it also keeps track of

2025-01-10 15:47:30
Internals//Physical Storage: Initialization Fork
  • References/Database/PostgreSQL/Internals/Physical Storage

Each unlogged table, and each index on an unlogged table, has an initialization fork. The initialization fork is an empty table or index of the appropriate type. When an unlogged

2025-01-10 15:47:30
Internals//Physical Storage: TOAST
  • References/Database/PostgreSQL/Internals/Physical Storage

This section provides an overview of TOAST (The Oversized-Attribute Storage Technique).

2025-01-10 15:47:30
Internals//Physical Storage: Database Page Layout
  • References/Database/PostgreSQL/Internals/Physical Storage

This section provides an overview of the page format used within PostgreSQL tables and indexes.[1] Sequences

2025-01-10 15:47:30
Internals//Physical Storage: Free Space Map
  • References/Database/PostgreSQL/Internals/Physical Storage

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

2025-01-10 15:47:30