#postgres18
Live, measured metrics for the hashtag #postgres18 from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #postgres18
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-29 02:38 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-29 02:38 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 02:38 UTCEverything below is measured over the latest 11 public posts (spanning ~6476 hours).
Posting hours (UTC)
Languages: English (11)
Avg boosts / post: 1.7
Top of the latest posts
Just published a new article on how to use UUIDv7 today with Python 3.14, Django 5.2 and PostgreSQL 18 🐍 I walk through Python generation, Django models, db_default, PostgreSQL functions, GeneratedField and even UUIDv47 for safer public ID
Did you know that UUIDv7 is also supported by Python 3.14? I along with my colleague Alexander Fridriksson are diving into some of the new features in #postgres18. We just released our look at UUIDv7. UUIDv7 is almost a no brainer for new p
The latest #Postgres release is just around the corner, and with it comes upgrades for everything from performance, security, developer experience, and beyond. 🚀 Get the full breakdown of what's in the works from a dev's perspective in our
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/postgres18