PostgreSQL compatibility: time + interval should wrap within the 24-hour time domain

Split out from #22247.

Mismatch

time + interval should wrap within the 24-hour time domain.

SELECT time '23:30' + interval '2 hours';

PostgreSQL:

01:30:00

DataFusion:

25 hours 30 mins

Expected behavior

For PostgreSQL-compatible SQL semantics, DataFusion should either match PostgreSQL's result or raise the same class of domain/semantic error.

take

untake

memory D SELECT time '23:30' + interval '2 hours';
┌───────────────────────────────────────────────────────┐
│ (CAST('23:30' AS TIME) + CAST('2 hours' AS INTERVAL)) │
│                         time                          │
├───────────────────────────────────────────────────────┤
│ 01:30:00                                              │
└───────────────────────────────────────────────────────┘

Opened #23279 for this. time + interval now returns a wrapped time (23:30 + 2h → 01:30) instead of an interval, following the existing Date - Date handling. Open to feedback.

fix: `time ± interval` returns a wrapped `time` instead of an interval

fix: `time ± interval` returns a wrapped `time` instead of an interval (

Navigation Menu

Repository navigation

PostgreSQL compatibility: `time + interval` should wrap within the 24-hour time domain #22265

Mismatch

Expected behavior

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

PostgreSQL compatibility: time + interval should wrap within the 24-hour time domain #22265

Description

Mismatch

Expected behavior

Activity

tarekakrout2021 commented on May 16, 2026

tarekakrout2021 commented on May 16, 2026

kumarUjjawal commented on May 18, 2026

vismaytiwari commented on Jul 1, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

PostgreSQL compatibility: `time + interval` should wrap within the 24-hour time domain #22265