PostgreSQL 17.3, Siren Call of SQLite on the Server, and More on Databases
-
PostgreSQL ☛ PostgreSQL 17.3, 16.7, 15.11, 14.16, and 13.19 Released!
The PostgreSQL Global Development Group has released an update to all supported versions of PostgreSQL, including 17.3, 16.7, 15.11, 14.16, and 13.19.
-
[Repeat] Ruben Schade ☛ Limits before running Postgres becomes useful
I say this as a recent(ish) convert, but there are very few situations where a personal project will ever reach the scale where Postgres is necessary. The truth is: [...]
-
Malcom Coles ☛ Siren Call of SQLite on the Server
The thing is…just don’t run SQLite server-side in production. Unless you have a really good reason.
It isn’t because SQLite might lose your data (it won’t), or it doesn’t scale well (it scale’s just fine), it’s because using SQLite as your primary data store just makes your life harder.
Why?
Prior to release:
-
Out-of-cycle release scheduled for February 20, 2025
The PostgreSQL Global Development Group is planning for an out-of-cycle release on February 20, 2025 to address a regression that was released as part of the February 13, 2025 update release, which included release 17.3, 16.7, 15.11, 14.16, and 13.19. As part of this release, we will issue fixes for all supported versions (17.4, 16.8, 15.12, 14.17, 13.20). While these fixes may not impact all PostgreSQL users, PostgreSQL Global Development Group determined that it would be better to address these sooner than the next scheduled release on May 8, 2025.