Re: uuidv7 improperly accepts dates before 1970-01-01
Kyotaro Horiguchi <horikyota.ntt@gmail.com>
From: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
To: baji.pgdev@gmail.com
Cc: zsolt.parragi@percona.com, pgsql-hackers@lists.postgresql.org
Date: 2026-06-26T04:57:41Z
Lists: pgsql-bugs, pgsql-hackers
Thank you for the new version. At Thu, 25 Jun 2026 08:47:27 -0500, Baji Shaik <baji.pgdev@gmail.com> wrote in > 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. Personally, I still feel that providing the UUIDv7 timestamp domain in an errdetail is a bit excessive. Even for infinity, I tend to think of the issue as simply being outside the representable range, so I'm not sure that a separate message is necessary. That said, this feels like a matter of taste, so it would probably be useful to hear other opinions. Regards, -- Kyotaro Horiguchi NTT Open Source Software Center
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
COPY TO FORMAT JSON: respect column list order
- effb923d9dec 19 (unreleased) landed