pg_uuidv7
discussion
| pg_uuidv7 | discussion | |
|---|---|---|
| 4 | 4 | |
| 242 | 79 | |
| - | - | |
| 7.4 | 1.8 | |
| about 2 months ago | almost 2 years ago | |
| C | ||
| Mozilla Public License 2.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pg_uuidv7
-
Shrink UUIDs with PostgreSQL or Ruby
Unfortunately, as of PostgreSQL 16, UUIDv7 are not yet supported out of the box. For the time being, use an extension such as pg_uuidv7 or pg_idkit to generate UUIDv7 e.g. as default primary key when you CREATE new records.
-
UUIDv7 is coming in PostgreSQL 17
https://github.com/fboulnois/pg_uuidv7
It's slightly different from recommendations by draft RFC version (there's no counter), but fully within spec requirements. From practical point there's no difference at all.
- Are there trusted non-cryptographic hashing extensions for Postgresql?
-
UUIDs are obsolete in the age of Docker
Sometimes, I am amazed about what gets on the front page of ycombinator.
TLDR: Don't use UUID v1, since its entropy is based on the Mac address, if your cloud provider is generating the same mac addresses for all your containers.
To say not use UUID's it makes no sense. Use UUIDv7, use them in postgres https://github.com/fboulnois/pg_uuidv7 have fun :)
discussion
-
UUIDv7 is coming in PostgreSQL 17
> Integers don't scale because you need a central server to keep track of the next integer in the sequence.
They most assuredly do scale. [0]
Also, Slack is built on MySQL + Vitess [1], the same system behind PlanetScale, which internally uses integer IDs [2].
[0]: https://www.enterprisedb.com/docs/pgd/latest/sequences/#glob...
[1]: https://slack.engineering/scaling-datastores-at-slack-with-v...
[2]: https://github.com/planetscale/discussion/discussions/366
-
HELP: GitHub, PlanetScale(MySQL), and Dashboards
Some context avail at https://github.com/planetscale/discussion/discussions/186
- How do I maintain referential integrity?
-
Vitess 11
Please prioritize the standard connection string access method: https://github.com/planetscale/beta/discussions/15
This single feature would open up a lot of usage for me and many others I know.
What are some alternatives?
pg_math - pg_math extension to support statistical distribution functions for PostgreSQL
pg_auto_failover - Postgres extension and service for automated failover and high-availability
vasco - vasco: Discover hidden patterns in your Postgres data
patroni - A template for PostgreSQL High Availability with Etcd, Consul, ZooKeeper, or Kubernetes
orchestrator - MySQL replication topology management and HA