DrakoRod 🇲🇽

Al margen de la coyuntura, yo creí que no ver TV Azteca era una práctica básica de higiene cognitiva.

Si esto es cierto! gracias mil gracias Uganda! feliz!

Stay tuned for next level scaling #PostgreSQL

We're hiring "Software Engineer - Postgres Internals" to work on my team at @PlanetScale. Let's help the community to make @PostgreSQL even better for more 30years. job-boards.greenhouse.io/planetscale/jo…

Jajajajaja yo soy el code review 1 y mi partner es el dos haha #PostgreSQL

UPDATE: pgBackRest is likely to receive enough funding be be revived. See github.com/pgbackrest/pgb… for details.

😥

CFOs realizing that their AI token budget is going to be higher than the salaries of the people they laid off

jajaja es gracioso porque es verdad

True story 🤣

PgQue v0.1.0 is out. PgQ -- the Postgres queue system built at Skype 20 years ago for 1B-user-scale workloads -- repackaged for the managed-Postgres era. One SQL file. No C extension. No external daemon. pg_cron to tick. Why bother reviving a 2007 architecture? Every major Postgres queue in production today uses some flavor of SKIP LOCKED + UPDATE/DELETE. It works under light load. When you have more data and higher load, it degrades predictably. Then you get posts like these: - Brandur at Heroku, 2015: 60k job backlog in one hour from a single open transaction - PlanetScale, 2026: death spiral at 800 jobs/sec - River issue #59, awa issue #169 and so on, Oban's partitioning work, PGMQ's autovacuum tuning guide and duct-taping with pg_partman The core issue is how Postgres MVCC is implemented and how we deal with it. Dead tuples in the hot path, xmin horizon pinned, vacuum falling behind, query performance quickly degrades. This happens every time you run pg_dump, execute an analytical query, or have a lagging/unused logical replication slot. PgQ solved this in 2007 with snapshot-based batching and TRUNCATE rotation -- zero dead tuples in the event path, by design. But PgQ needed a C extension and an external daemon. Which means it doesn't run on RDS, Aurora, Cloud SQL, AlloyDB, Supabase, or Neon -- i.e., where most Postgres lives now. PgQue closes that gap. 💎 Pure SQL + PL/pgSQL (PgQ engine) 👩‍💻 \i sql/pgque.sql -- you're done 🕑 pg_cron replaces pgqd (optional, recommended) 💻 Python, Go, TypeScript client examples shipped 💙 Apache 2.0 Trade-off: end-to-end event delivery latency is up to a second, it depends on ticking frequency. If you need sub-3ms job dispatch, use River, Oban, or graphile-worker (and avoid anything that blocks xmin horizon). If you need high-throughput event streaming with fan-out inside Postgres -- Kafka-shaped, without Kafka and dealing with transactional outbox implementation -- this is the right shape of tool. Kudos to Marko Kreen and Skype engineers who implemented this decades ago, for the original PgQ, and to Alexander Kukushkin whose recent "Rediscovering PgQ" talk brought this quiet corner of the Postgres ecosystem back into view. Stars, issues, PRs, and honest criticism all welcome. Link 👇

Taiob Ali, Microsoft Data Platform MVP, compares PostgreSQL & SQL Server security models, including differences in how these databases handle user authentication, roles, & permissions. Register for updates to POSETTE 2026 Livestream 1 on Tue 16 Jun posetteconf.com/2026/talks/pos…

Jajaja lo somos 😎

Ya que truene la burbuja IA y empiece la burbuja minería espacial 🚀

Jeremy Schneider (@jer_s): How Blocking-Lock Brownouts Can Escalate from Row-Level to Complete System Outages postgr.es/p/7qE

Feliz Día del Backup 🔒📁 #backupday Para celebrar, hay descuento en la tienda @sysarmy👇 10% OFF con el código NOHAYBACKUP, solo por hoy en tienda.sysarmy.com

This is the coolest thing that I saw in the postgres world in a few years.

Hubert 'depesz' Lubaczewski: Waiting for PostgreSQL 19 – Introduce the REPACK command postgr.es/p/7vl

Shaun Thomas: Using Patroni to Build a Highly Available Postgres Cluster—Part 3: HAProxy postgr.es/p/7vT

PostgreSQL 19 dev: SQL Property Graph Queries (SQL/PGQ) Author: Peter Eisentraut, Ashutosh Bapat git.postgresql.org/gitweb/?p=post…