When CAST a TIMESTAMP(x) value AS TIMESTAMP(y), and x > y, the decimal part that exceeds the accuracy will be directly ignored instead of rounding. about duckdb HOT 2 CLOSED

EDIT: misread the results. PostgreSQL does round up.

This behavior is

• consistent with DECIMAL:

SELECT
33.846::DECIMAL(4, 2)

┌──────────────────────────────┐
│ CAST(33.846 AS DECIMAL(4,2)) │
│         decimal(4,2)         │
├──────────────────────────────┤
│                        33.84 │
└──────────────────────────────┘

• inconsistent with PostgreSQL: https://www.db-fiddle.com/f/8K9U6dudJLxsVujbZFHMkQ/0

from duckdb.

Decimal would be a separate issue, but yes PG does round timestamps:

hawkfish=# select cast('2024-05-10 11:06:33.846' as timestamp(0));
      timestamp      
---------------------
 2024-05-10 11:06:34

from duckdb.