PostgreSQL compatibility: factorial(21) should not overflow when PostgreSQL returns a numeric answer

Split out from #22247.

Mismatch

factorial(21) should not overflow when PostgreSQL returns a numeric answer.

SELECT factorial(21);

PostgreSQL:

51090942171709440000

DataFusion:

Overflow happened on FACTORIAL(21)

Expected behavior

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

take

duckdb

memory D SELECT factorial(21);
┌──────────────────────┐
│    factorial(21)     │
│        int128        │
├──────────────────────┤
│ 51090942171709440000 │
└──────────────────────┘
memory D

another datapoint is that it seems spark returns factorial as long, instead of decimal

https://github.com/apache/spark/blob/a100c0bfe5e749442620901ee20d1dc1b9b47aba/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/mathExpressions.scala#L660-L704

Navigation Menu

Repository navigation

PostgreSQL compatibility: `factorial(21)` should not overflow when PostgreSQL returns a numeric answer #22259

Mismatch

Expected behavior

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

PostgreSQL compatibility: factorial(21) should not overflow when PostgreSQL returns a numeric answer #22259

Description

Mismatch

Expected behavior

Activity

xiedeyantu commented on May 16, 2026

kumarUjjawal commented on May 18, 2026

Jefffrey commented on May 26, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

PostgreSQL compatibility: `factorial(21)` should not overflow when PostgreSQL returns a numeric answer #22259