PostgreSQL Performance & Query Optimization · Lektion

Abdeckende Indizes und Index-Only-Scans

Entdecken Sie, wie abdeckende Indizes den Tabellenzugriff vermeiden und hocheffiziente Index-Only-Scans ermöglichen.

Abdeckende Indizes und Index-Only-Scans ist eine kostenlose PostgreSQL Performance & Query Optimization-Lektion auf CoddyKit. Dies ist Lektion 3 von 4. Du kannst die komplette Lektion unten kostenlos lesen – dann übst du sie direkt im Browser mit einem integrierten Code-Editor und einem KI-Tutor rund um die Uhr. Sie ist Teil des PostgreSQL Performance & Query Optimization-Lernpfads, und dein Fortschritt wird über Web und CoddyKit-App synchronisiert. Der PostgreSQL Performance & Query Optimization-Kurs umfasst insgesamt 4 Lektionen.

Teile dieser Lektion wurden noch nicht übersetzt und werden auf Englisch angezeigt.

What are Covering Indexes?

Welcome to our lesson on Covering Indexes and Index-Only Scans! These advanced indexing techniques can dramatically boost your PostgreSQL query performance.

A regular index helps PostgreSQL quickly find rows based on certain column values. Think of it like a book's index: it tells you which page to go to for a topic.

The Cost of Table Access

When you use a standard index, PostgreSQL first finds the row's location (its tuple ID or CTID) in the index. Then, it has to go to the actual table to fetch the rest of the data for that row.

This extra step, called a table lookup or heap fetch, can be slow, especially if many rows are involved or if the table data isn't in memory.

Indexing All You Need

A covering index is an index that contains all the columns needed to fulfill a query, not just the columns in the WHERE clause. This means PostgreSQL can answer the query by reading only the index, without ever touching the main table data.

It 'covers' the query's data requirements entirely.

Building a Covering Index

To create a covering index, you include all the columns your query might select or filter on. PostgreSQL supports including non-key columns using the INCLUDE clause, which stores them without making them part of the primary sort key.

Let's create a table and then a covering index.

CREATE TABLE products (
  product_id SERIAL PRIMARY KEY,
  name VARCHAR(100) NOT NULL,
  price DECIMAL(10, 2) NOT NULL,
  category VARCHAR(50)
);

INSERT INTO products (name, price, category) VALUES
('Laptop', 1200.00, 'Electronics'),
('Keyboard', 75.00, 'Accessories'),
('Mouse', 25.00, 'Accessories'),
('Monitor', 300.00, 'Electronics');

-- Covering index for queries on category that also select name and price
CREATE INDEX idx_products_category_cover_name_price
ON products (category) INCLUDE (name, price);

Introducing Index-Only Scans

When a query can be fully satisfied by a covering index, PostgreSQL performs an Index-Only Scan. This is a highly efficient operation because the database engine doesn't need to read any data blocks from the main table (the 'heap').

It's like finding all the information you need directly in the book's index, without ever turning to the main chapters.

MVCC & Index-Only Scans

PostgreSQL uses MVCC (Multi-Version Concurrency Control). For an Index-Only Scan to work, PostgreSQL must ensure that the versions of the rows it finds in the index are visible to the current transaction.

It does this by checking the table's visibility map, a special data structure that tracks which table pages contain only 'all-visible' tuples. If a page is marked all-visible, no heap fetch is needed to check row visibility.

Confirming with EXPLAIN

You can verify if PostgreSQL is using an Index-Only Scan by checking the query plan with EXPLAIN ANALYZE. Look for Index Only Scan in the output.

Let's try a query that our covering index should handle.

EXPLAIN ANALYZE
SELECT name, price
FROM products
WHERE category = 'Electronics';

Benefits: Speed & Efficiency

Index-Only Scans offer several key advantages:

Reduced Disk I/O: Fewer disk reads are needed because the main table is skipped.
Faster Query Execution: Less I/O directly translates to quicker query responses.
Better Cache Utilization: Indexes are often smaller and more frequently accessed, leading to better use of memory caches.
Concurrency: Less contention on table data blocks.

Trade-offs & Considerations

While powerful, covering indexes aren't a silver bullet:

Larger Indexes: Including more columns makes the index physically larger, consuming more disk space.
Slower Writes: Updates, inserts, and deletes to the main table also require updating the index, which can be slower for larger indexes.
Maintenance: Larger indexes might take longer to VACUUM.

Use them strategically for read-heavy queries that frequently access a specific subset of columns.

Practical Covering Index Example

Consider a `users` table where you often query user names and emails based on their registration date. An index on `registration_date` including `name` and `email` would be a perfect candidate for a covering index.

CREATE TABLE users (
  user_id SERIAL PRIMARY KEY,
  username VARCHAR(50) NOT NULL,
  email VARCHAR(100) NOT NULL,
  registration_date DATE NOT NULL
);

INSERT INTO users (username, email, registration_date) VALUES
('alice', 'alice@example.com', '2023-01-15'),
('bob', 'bob@example.com', '2023-02-20'),
('charlie', 'charlie@example.com', '2023-01-25');

CREATE INDEX idx_users_regdate_cover_name_email
ON users (registration_date) INCLUDE (username, email);

EXPLAIN ANALYZE
SELECT username, email
FROM users
WHERE registration_date BETWEEN '2023-01-01' AND '2023-01-31';

Quick Check: Index Scans

Based on what you've learned, identify the correct statements about Index-Only Scans in PostgreSQL.

Recap: Covering Indexes

You've learned that covering indexes include all columns needed by a query, enabling highly efficient Index-Only Scans. These scans bypass the main table, significantly reducing disk I/O and speeding up read-heavy queries.

Remember to use EXPLAIN ANALYZE to confirm their usage and consider the trade-offs of increased index size and potential write overhead. Happy optimizing!

Häufig gestellte Fragen

Ist die Lektion „Abdeckende Indizes und Index-Only-Scans“ kostenlos?

Ja — der vollständige Text von „Abdeckende Indizes und Index-Only-Scans“ ist hier im Web kostenlos zu lesen. Um sie interaktiv zu üben (integrierter Code-Editor und 24/7 KI-Tutor) und den Rest des PostgreSQL Performance & Query Optimization-Kurses freizuschalten, upgrade auf CoddyKit PRO. Der PostgreSQL Performance & Query Optimization-Kurs umfasst insgesamt 4 Lektionen.

Was lerne ich in „Abdeckende Indizes und Index-Only-Scans“?

Entdecken Sie, wie abdeckende Indizes den Tabellenzugriff vermeiden und hocheffiziente Index-Only-Scans ermöglichen. Du übst PostgreSQL Performance & Query Optimization mit praktischem Code, den du direkt im Browser ausführst, und ein 24/7 KI-Tutor beantwortet deine Fragen während du die Lektion bearbeitest.

Brauche ich Erfahrung, um PostgreSQL Performance & Query Optimization zu starten?

Keine Vorkenntnisse erforderlich. PostgreSQL Performance & Query Optimization auf CoddyKit ist für Anfänger bis fortgeschrittene Lernende strukturiert, sodass du hier starten oder von Anfang an beginnen und in deinem eigenen Tempo voranschreiten kannst. Dies ist Lektion 3 von 4.

Wie lange dauert die Lektion „Abdeckende Indizes und Index-Only-Scans“?

Die meisten CoddyKit-Lektionen dauern etwa 5–10 Minuten. Jede ist kompakt und interaktiv, sodass du stetig Fortschritte machst und genau dort weitermachst, wo du aufgehört hast – im Web und in der App.

Kann ich in dieser PostgreSQL Performance & Query Optimization-Lektion Code schreiben und ausführen?

Ja. Jede PostgreSQL Performance & Query Optimization-Lektion enthält einen integrierten Code-Editor, sodass du echten Code direkt in deinem Browser schreibst und ausführst und sofort KI-Feedback erhältst — ohne lokale Einrichtung erforderlich.

Alle Lektionen in diesem Kurs

Hash-, GIN- und GiST-Indizes
Partielle und Ausdrucksindizes
Abdeckende Indizes und Index-Only-Scans
BRIN-Indizes für große sequenzielle Datenmengen

← Zurück zu PostgreSQL Performance & Query Optimization