POSTGRESQL RANGE TYPES

A range type in PostgreSQL represents a continuous interval of values as a single data type.

Instead of storing two separate columns like `start_date` and `end_date`, PostgreSQL allows you to store the interval in one logical field such as `period daterange`. A range is a first-class datatype, fully supported by operators, indexes, and constraints.

Built-in Range Types

PostgreSQL provides the following native range types:

Basic Range Syntax

A range is defined using brackets:

[ lower , upper ]

Empty Ranges

 An empty range represents a valid range value containing no elements.  

SELECT 'empty'::int4range;

Unbounded Ranges

 Ranges can be open-ended on either side.  

SELECT '[2025-01-01,)'::daterange;

SELECT '(,2025-01-01]'::daterange;

Range Constructors

 Ranges can also be built using constructor functions instead of literals.  

SELECT daterange('2025-01-01', '2025-12-31', '[)');

General syntax:

range_type(lower, upper, bounds)

Core Logical Operators

PostgreSQL provides rich built-in operators for range processing:

Core Functions

 A set of built-in functions allows extracting and analyzing range properties.  

Short description of gist and sp-gist indexes, we will review then separately.

Indexing Range Types – GiST

 For most range-based operations PostgreSQL uses GiST indexes, which are designed for non-standard comparisons such as overlap and containment.  

CREATE INDEX ON table USING gist (range_column);

This index supports:

• overlap checks
• containment checks
• adjacency checks
• exclusion constraints

Alternative Index Type – SP-GiST

 SP-GiST is another index type that can sometimes be more compact or efficient depending on data distribution.  

CREATE INDEX ON table USING spgist (range_column);

Choice between GiST and SP-GiST depends on workload characteristics.

Real Business Scenarios

Range types are ideal for systems dealing with:

• employment periods
• insurance coverage intervals
• product pricing validity
• hotel or resource reservations
• promotions and campaigns
• tax rate validity
• interest rate schedules

Any domain involving time intervals or numeric intervals benefits directly from range types.

PostgreSQL vs Other RDBMS – Feature Comparison

Functional Equivalents in Other Databases

 To simulate PostgreSQL range behavior in Oracle, SQL Server, or MySQL, developers must store two separate columns.  

Instead of:

period daterange

Other databases must use:

start_date DATE,

end_date DATE

And manually emulate overlap logic:

WHERE new.start <= existing.end

AND new.end >= existing.start

This approach is:

• error-prone
• harder to maintain
• not index-friendly
• not constraint-safe
• more complex to optimize

PostgreSQL range types provide:

• correctness by design
• declarative interval logic
• built-in operators
• proper index support
• seamless constraint integration
• safer concurrency handling

 Other RDBMS platforms can only imitate this behavior using manual patterns such as triggers, stored procedures, or complex application logic. PostgreSQL delivers the functionality natively at the database engine level.