FAfastball·Nov 10, 2021
Here's one[1], not actively maintained though.
[1] https://github.com/edoceo/pg-ulid
In Lesser-known Postgres featuresedoceo
pg-ulid
C2021–2021
edoceo / pg-ulid
pg-ulid
ULID Functions for PostgreSQL
2Distinct people
2Mentions
0Explicit recommenders
61GitHub stars
What to know before exploring
What it is
ULID Functions for PostgreSQL
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by week2 dated mentions
Observed mentions: 2021-06-01 06:57:35 UTC to 2021-11-10 01:47:12 UTC. Weeks start Monday, UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| May 31 | 2021-05-31 00:00:00 UTC | 2021-06-07 00:00:00 UTC | 1 | 0 | 1 |
| Jun 7 | 2021-06-07 00:00:00 UTC | 2021-06-14 00:00:00 UTC | 0 | 0 | 0 |
| Jun 14 | 2021-06-14 00:00:00 UTC | 2021-06-21 00:00:00 UTC | 0 | 0 | 0 |
| Jun 21 | 2021-06-21 00:00:00 UTC | 2021-06-28 00:00:00 UTC | 0 | 0 | 0 |
| Jun 28 | 2021-06-28 00:00:00 UTC | 2021-07-05 00:00:00 UTC | 0 | 0 | 0 |
| Jul 5 | 2021-07-05 00:00:00 UTC | 2021-07-12 00:00:00 UTC | 0 | 0 | 0 |
| Jul 12 | 2021-07-12 00:00:00 UTC | 2021-07-19 00:00:00 UTC | 0 | 0 | 0 |
| Jul 19 | 2021-07-19 00:00:00 UTC | 2021-07-26 00:00:00 UTC | 0 | 0 | 0 |
| Jul 26 | 2021-07-26 00:00:00 UTC | 2021-08-02 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2 | 2021-08-02 00:00:00 UTC | 2021-08-09 00:00:00 UTC | 0 | 0 | 0 |
| Aug 9 | 2021-08-09 00:00:00 UTC | 2021-08-16 00:00:00 UTC | 0 | 0 | 0 |
| Aug 16 | 2021-08-16 00:00:00 UTC | 2021-08-23 00:00:00 UTC | 0 | 0 | 0 |
| Aug 23 | 2021-08-23 00:00:00 UTC | 2021-08-30 00:00:00 UTC | 0 | 0 | 0 |
| Aug 30 | 2021-08-30 00:00:00 UTC | 2021-09-06 00:00:00 UTC | 0 | 0 | 0 |
| Sep 6 | 2021-09-06 00:00:00 UTC | 2021-09-13 00:00:00 UTC | 0 | 0 | 0 |
| Sep 13 | 2021-09-13 00:00:00 UTC | 2021-09-20 00:00:00 UTC | 0 | 0 | 0 |
| Sep 20 | 2021-09-20 00:00:00 UTC | 2021-09-27 00:00:00 UTC | 0 | 0 | 0 |
| Sep 27 | 2021-09-27 00:00:00 UTC | 2021-10-04 00:00:00 UTC | 0 | 0 | 0 |
| Oct 4 | 2021-10-04 00:00:00 UTC | 2021-10-11 00:00:00 UTC | 0 | 0 | 0 |
| Oct 11 | 2021-10-11 00:00:00 UTC | 2021-10-18 00:00:00 UTC | 0 | 0 | 0 |
| Oct 18 | 2021-10-18 00:00:00 UTC | 2021-10-25 00:00:00 UTC | 0 | 0 | 0 |
| Oct 25 | 2021-10-25 00:00:00 UTC | 2021-11-01 00:00:00 UTC | 0 | 0 | 0 |
| Nov 1 | 2021-11-01 00:00:00 UTC | 2021-11-08 00:00:00 UTC | 0 | 0 | 0 |
| Nov 8 | 2021-11-08 00:00:00 UTC | 2021-11-15 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
2 sourcesYeah, just use a UUID unless the bits to store the UUID really are your driving limitation (they're not), having a UUID that is non-linear is almost always the most straight-forward option for identifying things, for the tradeoff of human readability (though you can get some of that back with prefixes and some other schemes). I'm not going to rehash the benefits that people have brought up for UUIDs, but they're in this thread. At this point what I'm concerned about is just... what is the best kind of UUID to use -- I've recently started using mostly v1 because time relationship is important to me (despite the unfortunate order issues) and v6[0] isn't quite so spread yet. Here's a list of other approaches out there worth looking at
- isntauuid[1] (mentioned in this thread, I've given it a name here)
- timeflake[2]
- HiLo[3][4]
- ulid[5]
-
Read the rest
ksuid[6] (made popular by segment.io)
- v1-v6 UUIDs (the ones we all know and some love)
- sequential interval based UUIDs in Postgres[7]
Just add a UUID -- this almost surely isn't going to be what bricks your architecture unless you have some crazy high write use case like time series or IoT or something maybe.
[0]: http://gh.peabody.io/uuidv6/
[1]: https://instagram-engineering.com/sharding-ids-at-instagram-...
[2]: https://github.com/anthonynsimon/timeflake
[3]: https://en.wikipedia.org/wiki/Hi/Lo_algorithm
[4]: https://www.npgsql.org/efcore/modeling/generated-properties....
[5]: https://github.com/edoceo/pg-ulid
[6]: https://github.com/segmentio/ksuid
[7]: https://www.2ndquadrant.com/en/blog/sequential-uuid-generato...