Making Postgres 42,000x slower because I am unemployed - by Jacob Jackson

https://byteofdev.com/posts/making-postgres-slow/

Hm. I normally use https://github.com/pgautoupgrade/docker-pgautoupgrade whenever I need to deploy a #postgres container because I can just increase the version in my #Ansible playbooks to perform an upgrade.

Now I need #postgis for #dawarich and there doesn't seem to be such a convenient fork to ease future upgrades.

Am I missing something? Do I really want to bother future-me with manual upgrades that may include dumping, updating and restoring? Or would I just add these steps to my playbook?

I've used #MySQL before (last time was 2016, I think), but today I'm mostly onto #Postgres (and sometimes, #SQLite). I know PG is superior to MySQL is pretty much all aspect I could think of, but still, it seems that MySQL still has a quite big user base.

What's the catch? What am I missing here? Why would someone use MySQL over Postgres to build smt since Postgres [apparently] is better than MySQL in every single possible aspect?

It's a honest question. Please help me understand it – and perhaps, consider modern MySQL/MariaDB in next projects. :)

Install and run a PostgreSQL database locally on Linux, MacOS or Windows. PostgreSQL can be bundled with your application, or downloaded on demand.

This library provides an embedded-like experience for PostgreSQL similar to what you would have with SQLite.

https://github.com/theseus-rs/postgresql-embedded

The use of #postgres notify/listen shouldn't be with multiple writers.

Immensely powerful utility, but terrible if you try to do multiple execution in parallel through transactions. Although if you use triggers, you can have multi writers, but you lose atomic op.

https://www.recall.ai/blog/postgres-listen-notify-does-not-scale

In testing a postgres upgrade (13->15) for our mastodon-servcer, I run into a fatal error 'Your installation contains user-defined objects that refer tointernal polymorphic functions with arguments of type "anyarray" or "anyelement". Haven't been able to find a fix for this online, and there seems to be no logfile to pinpoint the cause. Anyone have any suggestions on how to fix this? #techquestion #mastoadmin #postgres [Edit: solved, see reply]

Dear #Fediverse, I need your recommendation:

I'm building a #website that in the end consists of a #Docker #NodeJS image/container and a #Postgres container. What options are there to host those containers on the #Web? I'm looking for a cheap or even free (?!) solution. I expect less than 50 users, so big hardware or scalability is not an issue. Would a virtual server with #minikube be a viable option? I'm a Docker and #Kubernetes newb so please bear with me.

You will never forget the first time you saw a 30-table join spanning 30 systems in a single query.

https://coffingdw.com/30-table-join-across-30-different-systems-shocks-the-it-world/

pro tip for user interface designers:

if you have hundreds of millions of dollars of venture capital and you want to make a user facing data analytics tool of some kind and you think it's reasonable to ask an average human being to type this:

CAST('2023-05-01' AS TIMESTAMP)

to do literally anything with a date or time in your application's user interface, just stop right there. do not pass go, do not collect $200, and do not ever attempt to offer feedback to a UX designer ever again. something is deeply broken inside you that means there are certain mysteries of the universe that even the guys who designed the postgres command line can access that you will never know, and that's ok. You can still live a really rad life.

AUTHOR UNBOXING: PostgreSQL Mistakes and How to Avoid Them! To celebrate the release of my book, you can use code PBAngelakos for 50% OFF until July 1st!

https://youtube.com/shorts/zopxHP1dznY

Order the book here from @ManningPublications http://mng.bz/D9mR

Watch how you can diagnose incidents in seconds using #opensource, #eBPF-powered observability.

Track all communications between cluster components such as #Patroni, #Postgres, #Pgbouncer, and the #Kubernetes API server: https://github.com/coroot/coroot

Please, someone tell me that you shouldn' upgrade #postgres directly

I'm so ready for #multigres.

#neon is already a scalable thing for #postgres. But this would be #Supabase take on the concept. Treating the problem, it seems, from sharding single tenant style.

https://supabase.com/blog/multigres-vitess-for-postgres

Yesterday I upgraded my Mastodon instance to go from PostgreSQL 15 PostgreSQL 17. The whole process was so simple that it almost seems silly to blog about it, but I did it anyway, in case anyone is interested:

https://blog.thms.uk/2025/06/upgrade-postgres-15-17-mastodon?utm_source=mastodon

Special thanks to @ruud who told me about link mode in pg_upgradecluster which was the missing piece I needed in oder to get the upgrade done with my limited disk space.

The extended deadline for our CFP is today! Submit your talk now and you could be a part of what is sure to be a fabulous lineup of speakers!

https://2025.pgconf.nyc/callforpapers/

@PostgreSQL #postgres #conference