Updated bucardo.org/postgres_all... - the all-in-one-page release notes. We just hit 555 versions of Postgres tracked! #postgres #postgresql

Heh, almost every first attempt at solving Advent of Code puzzles with Postgres leads to "ERROR: integer out of range". Poor little int4, just not up to the job! #postgres #postgresql #adventofcode

It's not just Postgres. Nulls are weird and full of edge cases no matter what RDBMS you use. #postgres #postgresql

Nice post about AI suggesting "improvements" for a Postgrs table schema. But the part that made me LOL was the human comment starting with "Hopefully" :) stokerpostgresql.blogspot.com/2025/10/load... #postgres #postgresql

Congrats!!

Oh for Pete's sake, now there are some on the Postgres lists advocating *raising* random_page_cost default - by a lot! Crazy times. #postgres #postgresql

Working on some v19 features and managed to break my test Postgres instance worst than I ever have before. Every single SQL command causes the backend to crash. To be fair, I'm messing with the parser, but it's still a little jarring. :) #postgres #postgresql

Been working with a database that defaults to UPPERCASE for unquoted things, and wow, is that annoying after all these decades of calm, non-yelling lowercase Postgres code. :) #postgres #postgresql

Wondering if I should bother trying to raise the default track_activity_query_size in Postgres. It's been 1kb for a long time, and that seems too small for today's verbose apps, complex queries, and ORMs. #postgres

Inspired by a Slack discussion, here's how to tell how many of today's 86,400 seconds have been used up already: select round(extract(epoch from now() - 'today'::date)); #postgres

Postgres Logging for Performance Optimization | Crunchy Data Blog Review key logging configurations in Postgres plus how to log key performance metrics.

Awesome blog post on Postgres logging from my colleague @sqlliz.bsky.social www.crunchydata.com/blog/postgre... #postgres #postgresql

Use of domains came up on Postgres lists recently. I very seldom use them, always seems better to just use check constraints on a base type. Still more useful than enum however! #postgres #postgresql

Yikes. Another crappy blog written by LLM spotted and slammed: thebuild.com/blog/2025/08... I'm not convinced the comment replies are not LLM as well. #postgres #postgresql

Getting down to the finish line - hope my "initdb checkpoints on by default" patch and its cousin "don't dump stats to pg_dump by default" both survive as is! #postgres #postgresql

Postgres tip of the day: you can chain psql -c calls:

psql -c 'alter system set random_page_cost = 1.5' -c 'select pg_reload_conf()'

Bonus: they run in the same session, so you can even use vars.

#postgres #postgresql

Not happy with all the ads and pseudo-ads popping up on Planet Postgres... #postgres #postgresql

Making Postgres 42,000x slower because I am unemployed As an respectable unemployed person must do, I tried to make Postgres as slow as possible

Amazing post on making Postgres slower (yes, slower!) on purpose. byteofdev.com/posts/making... #postgres #postgresql Favorite bit: "random_page_cost = 1e300" LOL! Well done

Lessons from scaling PostgreSQL queues to 100K events This post is a chronicle of the critical, hard-won lessons learned while maturing PostgreSQL into a highly performant and resilient queuing system.

Great article at www.rudderstack.com/blog/scaling... about getting Postgres to scale. My only objection would be the lowering of checkpoint_timeout; better to rely on a failover replica than worry about WAL replay. #postgres #postgresql

Who are the PGDG? This article describes what the PGDG (PostgreSQL Global Development Group) is and how you can become a part of it.

Nice article about what exactly is the PGDG (Postgres Global Development Group). My sv is "anyone who directly (and knowingly) helps the project in any form". www.cybertec-postgresql.com/en/who-are-t... #postgres #postgresql #planetpg

Postgres making some more progress towards not supporting 32-bit stuff. Or at least making our code less painful to work with it. Even Raspberry Pi can do 64-bit these days! #postgres

Pro tip: use long args when sending example commands to someone; less likely they will get it wrong. psql -X vs. psql --no-psqlrc As a bonus, it's usually a lot more self-documenting as well. #postgres

Interesting thread on -hackers about Postgres resizing shared_buffers on the fly (smaller to larger only!). Looks quite feasible, I think it will make it into v19 #postgres

"While the Postgres community has an older and sometimes daunting contribution process of submitting patches to a mailing list..." (from clickhouse.com/blog/sigterm...). Okay, guilty as charged. :) #postgres

Love this post about active-active Postgres replication and reasons not to do it: percona.community/blog/2025/07... The best one is #4 (because other systems did it). If I had a nickle for every time I heard "but Oracle...." #postgres #postgresql

Fascinating discussion about Postgres and the use custom/generic plans (if you have been to my training, you know about this and the magic number 5). danolivo.substack.com/p/on-postgre... #postgres #postgresql #planetpg

This is a good post about UUIDs in Postgres at andyatkinson.com/constraint-d... but the name is too long - "Avoid UUID Version 4 Primary Keys" can really be shortened to "Avoid UUID" :) #postgres #postgresql

Good Postgres post on how often the optimizer is "correct": vondra.me/posts/how-of... #postgres #postgresql #planetpg Key qyote: "There’s also the question of the cost model itself, which is a very rough approximation of the hardware behavior" - I'm looking at you again, random_page_cost!!!

Woah - did not expect to see vectors in the (still future) SQL standard, but there it is: peter.eisentraut.org/blog/2025/06... #postgres #planetpg #postgresql

Cannot resist reposting this: devclass.com/2025/06/24/s... #postgres #postgresql

Nice article on SELECT FOR UPDATE in Postgres at www.cybertec-postgresql.com/en/select-fo.... I take issue that plain FOR UPDATE is "harmful" or "wrong", but I get the point about only taking the locks you actually need. Would be nice if NO KEY UPDATE was default. #postgres #planetpg #postgresql