On Wed, Jun 24, 2026 at 9:19 PM Kyotaro Horiguchi <[email protected]> wrote:
> From a user's perspective, it seems sufficient to know that the > shifted timestamp falls outside the range supported by UUID v7. As a > translator, I'm not particularly enthusiastic about adding more > message variants when the distinction is not particularly useful to > users. > Thanks for the feedback, Kyotaro. Good point. Attached v3 with all boundary checks using a single shared errdetail: "UUID version 7 supports timestamps from 1970-01-01 to approximately year 10889." 0001 - Reject infinite intervals 0002 - Reject pre-epoch timestamps (with overflow-safe epoch conversion) 0003 - Reject timestamps beyond the 48-bit limit I prefer keeping them as 3 patches since each addresses a distinct failure mode and is easier to review/bisect independently. That said, since 0002 and 0003 now share the same errdetail and are logically the same validation (timestamp outside valid range), I'm happy to merge them into one patch for v4 if preferred. Thanks, Baji Shaik.
v3-0002-Reject-pre-epoch-timestamps-in-uuidv7-interval.patch
Description: Binary data
v3-0001-Reject-infinite-intervals-in-uuidv7-interval.patch
Description: Binary data
v3-0003-Reject-timestamps-beyond-48-bit-limit-in-uuidv7-i.patch
Description: Binary data
