Amazon Redshift will no longer support the use of Python UDFs after June 30, 2026. We will start enforcing it in phases. For more information on the details of Python end of life and migration options, see the [ blog post ](https://aws.amazon.com/blogs/big-data/amazon-redshift-python-user-defined-functions-will-reach-end-of-support-after-june-30-2026/) that was published on June 30, 2025. 

# enable\_numeric\_rounding
<a name="r_enable_numeric_rounding"></a>

## Values (default in bold)
<a name="r_enable_numeric_rounding-values"></a>

on (true), **off (false)**

## Description
<a name="r_enable_numeric_rounding-description"></a>

Specifies whether to use numeric rounding. If `enable_numeric_rounding` is `on`, Amazon Redshift rounds NUMERIC values when casting them to other numeric types, such as INTEGER or DECIMAL. If `enable_numeric_rounding` is `off`, Amazon Redshift truncates NUMERIC values when casting them to other numeric types. For more information on numeric types, see [Numeric types](r_Numeric_types201.md).

## Example
<a name="r_enable_numeric_rounding-example"></a>

```
--Create a table and insert the numeric value 1.5 into it.
CREATE TABLE t (a numeric(10, 2));

INSERT INTO t VALUES (1.5);

SET enable_numeric_rounding to ON;
--Amazon Redshift now rounds NUMERIC values when casting to other numeric types.

SELECT a::int FROM t;

 a
---
 2
(1 row)


SELECT a::decimal(10, 0) FROM t;

 a
---
 2
(1 row)


 SELECT a::decimal(10, 5) FROM t;
 
    a
---------
 1.50000
(1 row)


SET enable_numeric_rounding to OFF;
--Amazon Redshift now truncates NUMERIC values when casting to other numeric types.

SELECT a::int FROM t;

 a
---
 1
(1 row)


SELECT a::decimal(10, 0) FROM t;

 a
---
 1
(1 row)


SELECT a::decimal(10, 5) FROM t;

    a
---------
 1.50000
(1 row)
```