Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Subject: BUG #19738: `uuidv7(interval)` rejects sub-millisecond timestamps
 within the final 48-bit millisecond
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:36:49 +0000
Message-ID: <19738-659d03aaa312f3b8@postgresql.org>
Auto-Submitted: auto-generated
Archived-At: 
 <https://www.postgresql.org/message-id/19738-659d03aaa312f3b8%40postgresql.org>
Precedence: bulk

The following bug has been logged on the website:

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

UUIDv7 stores a 48-bit Unix-millisecond timestamp, and PostgreSQL's
documentation says its timestamp also includes sub-millisecond precision. A
shifted timestamp 250 microseconds into the final representable millisecond
is
rejected as out of range, although its millisecond field is still the
maximum
valid value.

**Reproduction:**

```sql
SELECT uuidv7(
    (timestamptz '1970-01-01 UTC'
     + interval '281474976710655 milliseconds'
     + interval '250 microseconds')
    - clock_timestamp()
);
```

**Actual result:** SQLSTATE `22008`, `timestamp out of range for UUID
version 7`.

**Expected result:** Generate a UUIDv7 whose 48-bit millisecond timestamp is
`2^48 - 1`, preserving the permitted sub-millisecond component.