←
Álvaro Hernández10,899 posts
Álvaro Hernández avatar

Álvaro Hernández

@ahachete

Re-inventing databases @ongresinc (Founder). Passionate about Postgres, Cloud, Java and Open Source. Questioning conventional wisdom. For red pill followers.

◷ Joined February 2011▧ 437 Photos and videos
Nik Samokhvalov avatar
⟳ Álvaro Hernández retweeted
Nik Samokhvalov@samokhvalov·Nov 13

Watch full episode here: youtube.com/watch?v=gAdhpYew… - and let me know what you think about new format, that keeps evolving!

CREATE TEMP TABLE in every transaction: 3,931 tx/s 🐢 Same query as a CTE: 88,531 tx/s 🐘🚀 New Postgres FM with @yugedilbertfan and @samokhvalov: why it happens, and what to use instead With many idle sessions, DDL waits on LWLock:SInvalWrite Ever seen this one? thread 🧵👇

0:28
Luis avatar
⟳ Álvaro Hernández retweeted
Luis@Thor_luisXVII·Nov 9

Me han pedido que lo suba.

1:09
Postgres FM avatar
⟳ Álvaro Hernández retweeted
Postgres FM@PostgresFM·Nov 6

pgvector as its own container image: 0.31 MiB. A fat Postgres image with 18 extensions: 253 MiB. Both still cost the same restart to add. New episode with Álvaro Hernández @ahachete and Kirk Wolak @yugedilbertfan on extensions for Postgres in containers. New episode link👇

0:56
Álvaro Hernández avatar
Álvaro Hernández@ahachete·Oct 31

El sistema de seguridad que protegía a los trenes de colisionar se ha caído 170 veces en lo que llevamos de año (para que nos entendamos: día sí, día no). Y la seguridad pasaba a depender de los controladores. Así, el accidente, trágicamente, no es más que una consecuencia lógica. Poner vidas en riesgo a la espera de que el fallo humano se produzca. Esto es el resumen de lo que han hecho.

Álvaro Hernández avatar
Álvaro Hernández@ahachete·Oct 30

Oracle downloads are several GBs. Postgres downloads are ~ 30 MBs. If you didn't know yet, now you know which database to use in France. (and elsewhere, for that matter)

🔴 🇫🇷 ALERTE INFO - DU JAMAIS VU: UNE TAXE SUR CHAQUE GIGAOCTET INTERNET VOTÉE À L’ASSEMBLÉE Les députés ont adopté un amendement prévoyant de taxer les producteurs de données numériques à hauteur de 5,5 centimes par Go transmis. 💰 Objectif affiché : jusqu’à 10 milliards d’euros par an. Netflix, YouTube, cloud, jeux dématérialisés… les grands services numériques pourraient être concernés, avec un risque de répercussion sur les prix pour les consommateurs. 📌 Source : Assemblée nationale #France #Budget2027

Post attachmentPost attachment
Álvaro Hernández avatar
⟳ Álvaro Hernández retweeted
Álvaro Hernández@alvarohdezdp·Oct 29

1/ Esta mañana me dio por pensar cuánto me costaría montar una app para monitorizar los trenes de Renfe. Resulta que la posición GPS de cada tren es pública. 3-4 horas después, estaba funcionando 👇

Post attachment
Nik Samokhvalov avatar
⟳ Álvaro Hernández retweeted
Nik Samokhvalov@samokhvalov·Oct 28

pg_dump + pg_restore finished. Exit code 0. Row counts match. Your database is not ready yet. One query, 250M rows, Postgres 18.6, cold cache: → right after pg_restore: 32.6 s → after ANALYZE: 6.1 s → after VACUUM ANALYZE: 23 ms 💥 Same data. ~1,400× faster. A logical dump does not carry the visibility map, and by default not the planner statistics. 25 of 28 migration guides we checked don't say to run VACUUM after the load. Before traffic: vacuumdb --analyze --jobs 4 then ANALYZE each partitioned parent All tests are reproducible, and the scripts are in the post (bonus: podcast episode) 👇

Post attachment
Creston Jamison avatar
⟳ Álvaro Hernández retweeted
Creston Jamison@CrestonJamison·Oct 26

Scaling Postgres 440 is released! In this episode, we discuss how to reach 10 million queries per second efficiently, Postgres performance on GPUs, the next release of pgrust and not trusting ON DELETE CASCADE: scalingpostgres.com/episodes… #Postgres #PostgreSQL

Nik Samokhvalov avatar
⟳ Álvaro Hernández retweeted
Nik Samokhvalov@samokhvalov·Oct 25

your Postgres queue is fine until someone leaves a transaction open then SKIP LOCKED stops being a queue and becomes a dead-tuple factory we measured it at 1k events/s: - 4.1M dead tuples in 89 minutes - dequeue latency up ~3000x (!!) PgQue doesn't have this problem. at all. consumers never UPDATE or DELETE they just read. zero dead tuples -- engine built 20y ago at Skype, and served in large Postgres setups for two decades now revived in plain SQL to work anywhere 3.5 min, explained (sound on) 👇

3:30
Nik Samokhvalov avatar
⟳ Álvaro Hernández retweeted
Nik Samokhvalov@samokhvalov·Oct 21

something spiked 10 minutes ago. pg_stat_activity already forgot. pg_ash remembers. Active Session History for any Postgres -- pure SQL, no extension, no restart. RDS, Cloud SQL, Supabase, AlloyDB, Neon. in 2.0 (currently rc1): - redesigned to be easier to use, for humans and agents - unified AAS metrics - up to 23x faster reads tested on PG 14–19rc1 free, Apache 2.0 setup: \i sql/ash-install.sql select ash.start('1 second'); github.com/NikolayS/pg_ash -- ASH for Postgres, in pure SQL