A set of properties that guarantee database transactions are processed reliably: Atomicity (all operations succeed or fail together), Consistency (data integrity is maintained), Isolation (concurrent transactions don't interfere), and Durability (committed changes persist).
Read full glossary pageThe property that ensures all operations within a transaction are completed successfully, or none are applied at all.
Read full glossary pageContinuous shipping of WAL segments to durable storage for backups and PITR. Controlled by archive_mode and archive_command.
Read full glossary pageConfiguration parameter that specifies the shell command to execute to archive a completed WAL segment.
Read full glossary pageConfiguration parameter to enable WAL archiving. Values: off | on | always (for standbys).
Read full glossary pageA deployment model where software runs on the customer's own cloud infrastructure rather than the vendor's managed service.
Read full glossary pageA tree data structure that maintains sorted data and allows searches, sequential access, insertions, and deletions in logarithmic time.
Read full glossary pageLogical backups dump SQL/data (pg_dump), while physical backups copy data files/WAL (pg_basebackup, file system snapshots).
Read full glossary pageA consistent physical copy of a PostgreSQL cluster, typically taken with pg_basebackup, used with archived WAL for PITR.
Read full glossary pageA resource management technique where data is shared until one process needs to modify it, then a copy is created.
Read full glossary pageA technique to maintain a cache of database connections that can be reused across multiple requests.
Read full glossary pageA point in the WAL where all dirty data pages have been written to disk, providing a consistent recovery point.
Read full glossary pageA writable copy of a database or cluster, often created instantly using storage-level snapshots or COW.
Read full glossary pageA version control approach for databases that allows creating isolated copies for development, similar to Git branches.
Read full glossary pageThe ACID property ensuring that once a transaction is committed, it remains so even in the event of system failure.
Read full glossary pageA PostgreSQL command that shows the execution plan of a query along with actual runtime statistics.
Read full glossary pageA constraint that establishes a link between data in two tables by referencing the primary key of another table.
Read full glossary pageA technique for searching text data that goes beyond simple pattern matching to include linguistic analysis.
Read full glossary pageGeneralized Inverted Index - an index type in PostgreSQL optimized for indexing composite values like arrays and full-text search.
Read full glossary pageA standby server that can accept read-only queries while continuously applying WAL records from the primary.
Read full glossary pageAn approach that enables real-time analytics on transactional data without separate ETL processes.
Read full glossary pageA data structure that improves the speed of data retrieval operations on a database table.
Read full glossary pageThe ACID property that ensures concurrent transactions don't interfere with each other.
Read full glossary pagePostgreSQL data types for storing JSON documents. JSONB is a binary format that supports indexing and efficient operations.
Read full glossary pageA mechanism to control concurrent access to database resources to maintain data consistency.
Read full glossary pageA method of replicating data changes based on their logical representation rather than physical storage.
Read full glossary pageA byte position in the WAL stream that uniquely identifies a point in time for recovery or replication.
Read full glossary pageA technique that allows multiple transactions to access the same data simultaneously without blocking.
Read full glossary pageA database object that contains the result of a query and is physically stored, unlike a regular view.
Read full glossary pageA category of database processing that facilitates complex analytical queries over large datasets.
Read full glossary pageA category of database processing that manages transaction-oriented applications with high concurrency.
Read full glossary pagePostgreSQL's built-in benchmarking tool for running performance tests with simulated workloads.
Read full glossary pageA logical backup utility that exports a database's schema and/or data to a portable format (SQL, custom, directory).
Read full glossary pageA utility to restore backups created by pg_dump (custom, directory, tar formats), supporting parallelism and selective restore.
Read full glossary pageA tool to take a physical base backup of a running PostgreSQL cluster over the replication protocol.
Read full glossary pageRecovery of a cluster to an exact point in time or LSN using a base backup plus archived WAL and a recovery target.
Read full glossary pagePhysical backups copy data files/WAL (cluster-level); logical backups export SQL or data at the database/table level.
Read full glossary pageA constraint that uniquely identifies each row in a table and cannot contain NULL values.
Read full glossary pageA technique to split large tables into smaller, more manageable pieces based on specific criteria.
Read full glossary pageThe component of PostgreSQL that determines the most efficient way to execute a given SQL query.
Read full glossary pageThe process of copying and maintaining database objects in multiple database environments.
Read full glossary pageProcess of rebuilding a database or cluster from backups. Logical restore uses pg_restore; physical restore replays WAL.
Read full glossary pageConfiguration parameter that specifies how the server retrieves archived WAL files during recovery.
Read full glossary pageA recovery stop point defined by time, XID, name, or LSN to which PostgreSQL will recover during PITR.
Read full glossary pageA mechanism that retains WAL required by a subscriber or backup stream to prevent premature recycling.
Read full glossary pageThe ability to analyze data and provide insights immediately as data is created or updated.
Read full glossary pageA standardized language for managing and manipulating relational databases.
Read full glossary pageAn open-source backend platform that provides PostgreSQL database, authentication, and real-time subscriptions.
Read full glossary pageA standby.signal file in the data directory triggers standby mode in v12+, replacing recovery.conf.
Read full glossary pageA key performance metric measuring the number of database transactions completed per second.
Read full glossary pageA sequence of database operations that are executed as a single logical unit of work.
Read full glossary pageData organized by time order, typically used for metrics, logs, and sensor data.
Read full glossary pageA sequence identifier for WAL history used during recovery and replication; increments on divergence (e.g., PITR).
Read full glossary pageA single database system that can handle multiple workload types (OLTP, OLAP, search, etc.) efficiently.
Read full glossary pageAn operation that inserts a new row or updates an existing row if a conflict occurs.
Read full glossary pageA PostgreSQL maintenance operation that reclaims storage and updates statistics for optimal performance.
Read full glossary pageA search technique that finds similar items based on vector embeddings, commonly used for AI applications.
Read full glossary pageA high-performance PostgreSQL platform with instant cloning, Git-like branching, and unified OLTP/OLAP capabilities.
Read full glossary pageA logging mechanism where changes are written to a log before being applied to the database files.
Read full glossary pageA SQL clause used to filter records based on specified conditions.
Read full glossary page