PostgreSQL Performance & Query Optimization · Aula

Otimização de agregações e funções de janela

Aprenda técnicas para processar com eficiência agregações complexas e funções de janela.

Otimização de agregações e funções de janela é uma aula grátis de PostgreSQL Performance & Query Optimization no CoddyKit. Esta é a aula 1 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de PostgreSQL Performance & Query Optimization, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de PostgreSQL Performance & Query Optimization inclui 4 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

Aggregates & Windows Intro

Welcome to optimizing advanced queries! Today, we'll dive into making your aggregate and window functions run faster.

These powerful SQL features let you perform calculations across groups of rows or related rows. But, without care, they can become performance bottlenecks.

Aggregates Refresher

Aggregate functions summarize data for a group of rows, returning a single value per group. Common ones include COUNT(), SUM(), AVG(), MIN(), and MAX().

They often work with the GROUP BY clause to define these groups. Let's see a simple example:

SELECT
  category,
  COUNT(product_id) AS total_products
FROM
  products
GROUP BY
  category;

Window Functions Overview

Window functions also perform calculations across a set of table rows. However, unlike aggregates, they don't collapse rows. Instead, they return a result for each row in the original query.

They use an OVER() clause to define the 'window' of rows for the calculation. This window can be partitioned and ordered.

Optimizing Aggregates: Early Filtering

A key to fast aggregates is to process less data. Always filter your data as early as possible using the WHERE clause. This reduces the number of rows PostgreSQL needs to scan and group.

Consider this example where we only aggregate for 'Electronics':

SELECT
  category,
  AVG(price) AS avg_price
FROM
  products
WHERE
  category = 'Electronics'
GROUP BY
  category;

Optimizing Aggregates: Indexes for GROUP BY

Indexes can significantly speed up GROUP BY clauses. If an index exists on the column(s) used in GROUP BY, PostgreSQL can often use it to avoid sorting the entire dataset.

This is especially true for B-tree indexes, which store data in a sorted order.

CREATE INDEX idx_products_category
ON products (category);

Window Functions: PARTITION BY

The PARTITION BY clause within OVER() divides your dataset into independent groups, and the window function operates separately within each partition. Think of it like GROUP BY, but without collapsing rows.

Performance-wise, partitioning often involves sorting the data by the partition key(s), which can be resource-intensive for large datasets.

SELECT
  product_name,
  category,
  price,
  AVG(price) OVER (PARTITION BY category) AS avg_category_price
FROM
  products;

Window Functions: ORDER BY in Window

The ORDER BY clause inside OVER() defines the logical order of rows within each partition. This is crucial for ranking functions (like ROW_NUMBER()) and functions that depend on row order (like LAG(), LEAD()).

Just like with aggregates, this ordering step can be costly, especially if no suitable index exists to support the sort order.

SELECT
  product_name,
  category,
  price,
  ROW_NUMBER() OVER (PARTITION BY category ORDER BY price DESC) AS rank_in_category
FROM
  products;

Window Frames: ROWS and RANGE

Beyond PARTITION BY and ORDER BY, you can define a specific window frame using ROWS or RANGE. This specifies which subset of rows within the current partition the function should consider.

ROWS: Based on a fixed number of rows relative to the current row.
RANGE: Based on a value range relative to the current row's value.

Using a smaller, more precise window frame (e.g., ROWS BETWEEN 2 PRECEDING AND CURRENT ROW) often leads to better performance than larger, unbounded frames.

SELECT
  sale_date,
  amount,
  SUM(amount) OVER (
    ORDER BY sale_date
    ROWS BETWEEN 2 PRECEDING AND CURRENT ROW
  ) AS three_day_moving_avg
FROM
  sales;

General Optimization Tips

Here are some general tips for both aggregates and window functions:

Use appropriate indexes: Especially on GROUP BY, PARTITION BY, and ORDER BY columns.
Minimize data: Filter early with WHERE clauses.
Avoid complex expressions: Calculations inside aggregates/windows can be slow. Pre-calculate if possible.
Understand data distribution: Skewed data can lead to uneven work distribution and slow partitions.

Quick Check: Optimizing Aggregates

You have a large orders table and want to find the total amount for orders placed in '2023-01' for each customer. Which approach is generally more performant?

Recap & Next Steps

Great job! You've learned how to approach optimizing both aggregate and window functions.

Filter data early for aggregates.
Use indexes on GROUP BY, PARTITION BY, and ORDER BY columns.
Be mindful of the cost of sorting for both aggregates and window functions.
Define precise window frames with ROWS/RANGE when possible.

Keep these techniques in mind to write faster, more efficient PostgreSQL queries!

Perguntas Frequentes

A aula “Otimização de agregações e funções de janela” é grátis?

Sim — o texto completo de “Otimização de agregações e funções de janela” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de PostgreSQL Performance & Query Optimization, atualize para CoddyKit PRO. O curso de PostgreSQL Performance & Query Optimization inclui 4 aulas no total.

O que vou aprender em “Otimização de agregações e funções de janela”?

Aprenda técnicas para processar com eficiência agregações complexas e funções de janela. Você pratica PostgreSQL Performance & Query Optimization com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar PostgreSQL Performance & Query Optimization?

Nenhuma experiência prévia é necessária. PostgreSQL Performance & Query Optimization no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 1 de 4.

Quanto tempo leva a aula “Otimização de agregações e funções de janela”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de PostgreSQL Performance & Query Optimization?

Sim. Cada aula de PostgreSQL Performance & Query Optimization inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

Otimização de agregações e funções de janela
CTEs recursivas e consultas de grafos
Usando visões materializadas para melhorar o desempenho
Otimizando consultas com FILTER e agregação condicional

← Voltar para PostgreSQL Performance & Query Optimization