Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Subject: BUG #19741: `avg(double precision)` overflows on cancelling finite
 inputs whose mean is representable
To: pgsql-bugs@lists.postgresql.org
From: PG Bug reporting form <noreply@postgresql.org>
Cc: theshallow27@gmail.com
Reply-To: theshallow27@gmail.com, pgsql-bugs@lists.postgresql.org
Date: Fri, 02 Oct 2026 22:38:39 +0000
Message-ID: <19741-01386c4f17e36788@postgresql.org>
Auto-Submitted: auto-generated
Archived-At: 
 <https://www.postgresql.org/message-id/19741-01386c4f17e36788%40postgresql.org>
Precedence: bulk

The following bug has been logged on the website:

Bug reference:      19741
Logged by:          Shallow
Email address:      theshallow27@gmail.com
PostgreSQL version: 18.6
Operating system:   Linux
Description:       =20

The arithmetic mean of two finite values, `1e154` and `-1e154`, is exactly
zero. PostgreSQL's `avg(double precision)` raises an overflow instead. The
same input's sum is zero and its numeric average is zero. The aggregate's
shared float8 accumulation state appears to overflow while accumulating
values used for variance, although `avg` needs only the count and sum for
its
final result.

**Reproduction:**

```sql
SELECT avg(x)
FROM unnest(ARRAY[1e154, -1e154]::double precision[]) AS t(x);
```

**Actual result:** SQLSTATE `22003`, `value out of range: overflow`.

Reference calculation:

```sql
SELECT sum(x), avg(x::numeric)
FROM unnest(ARRAY[1e154, -1e154]::double precision[]) AS t(x);
-- 0 | 0
```

**Expected result:** `avg(double precision)` should return `0` for these
finite
inputs rather than failing due to an intermediate value that does not
contribute to the arithmetic mean.