Running experiments with ChatGPT asking it questions related to #PostgreSQL, 60% had incorrect or misleading information, and 20% had answers that would have caused (at best) performance reductions. One suggested that you can just delete WAL files if space is getting tight.
I find it increasingly difficult to self-host a #PostgreSQL database and have full confidence that it runs in a fully optimized way. There are so many settings, many targeting the underlying VM/hardware. Often I don't even have enough information about the VM/hardware to know what the most optimal settings are.
PostgreSQL devs are adding tons of new features and settings with every release.
There should be a lightweight "auto" mode where PG figures out the most appropriate settings with only a few hints.
But PG is now an enterprise RDBMS primarily targeting Oracle customers. Simplicity is not a quality they expect and I understand that.
I think it is time to explore the #SQLite route as an alternative. There is https://rqlite.io a fault-tolerant distributed SQLite server with an HTTP API written in Go, with automatic S3 backup and restore.
“In this walkthrough, we're going to use an Aiven for PostgreSQL database: we can create one, using the $300 and 30 days trial period, by accessing the aiven…”
I just published a short guide explaining how to upgrade PostgreSQL 🐘 from version 14 to 15 on Ubuntu 23.04 (Lunar Lobster) 🦞 after upgrading it from version 22.10 (Kinetic Kudu) 🐐