MAX OVER in Redshift

This page is a quick reference checkpoint for MAX OVER in Redshift: behavior, syntax rules, edge cases, and a minimal example; plus the official vendor documentation.


Function Details

MAX OVER returns the largest value in the window frame.

No behavioral details such as default frames or NULL-handling are described.

If this behavior feels unintuitive, the tutorial below explains the underlying pattern step-by-step.

MAX(expr) OVER (window) is supported; examples show PARTITION BY and ORDER BY within the window clause.

SELECT MAX(price) OVER (PARTITION BY category ORDER BY saletime) FROM sales;

What should you do next?

If you came here to confirm syntax, you’re done. If you came here to get better at window functions, choose your next step.

Understand the pattern

MAX OVER is part of a bigger window-function pattern. If you want the “why”, start here: Aggregate Window Functions

Prove it with a real query

Reading docs is useful. Writing the query correctly under pressure is the skill.

The Galactic Max Order Hunt

Support Status

  • Supported: yes
  • Minimum Version: Amazon Redshift auto-upgrades all clusters and does not publish SQL-by-version details, so minimum version is not applicable.

Official Documentation

For the authoritative spec, use the vendor docs. This page is the fast “sanity check”.

View Redshift Documentation →

Looking for more functions across all SQL dialects? Visit the full SQL Dialects & Window Functions Documentation.