it's funny that this is like, Veteran Wisdom, but as a general rule postgres is fine, and if you are using something that is not postgres you had better have a good reason why it's not postgres.
sqlite is fine as long as you know it's small
sqlite is fine as long as you know it's small
there is no reason to make a new database. postgres can do it. if you think postgres can't do it, you just haven't found the right way to enable it in pg_settings yet
November 2, 2026 at 6:21 AM
it's funny that this is like, Veteran Wisdom, but as a general rule postgres is fine, and if you are using something that is not postgres you had better have a good reason why it's not postgres.
sqlite is fine as long as you know it's small
sqlite is fine as long as you know it's small
Quick, release your own database that does everything postgres does, faster, and without all those bugs. Now's your chance
November 2, 2026 at 6:34 PM
Quick, release your own database that does everything postgres does, faster, and without all those bugs. Now's your chance
Jaz’s vlpds is pretty interesting. Postgres would likely have been fine. Foundationdb is worth a look
November 2, 2026 at 6:23 AM
Jaz’s vlpds is pretty interesting. Postgres would likely have been fine. Foundationdb is worth a look
Postgres 19's release is being stalled because LLMs are now finding so many bugs in it. From this we can conclude [insert 15 different thinkpieces, each of which makes everybody mad]
November 2, 2026 at 6:32 PM
Postgres 19's release is being stalled because LLMs are now finding so many bugs in it. From this we can conclude [insert 15 different thinkpieces, each of which makes everybody mad]
I've never seen Postgres described as overly fixated on velocity
November 2, 2026 at 6:43 PM
I've never seen Postgres described as overly fixated on velocity
*cries in My Employer Made A Good Decision On Postgres And Now It's Grown OLAP Workloads*
November 2, 2026 at 6:24 AM
*cries in My Employer Made A Good Decision On Postgres And Now It's Grown OLAP Workloads*
One shot a Postgres clone in Zig. No mistakes.
November 2, 2026 at 6:49 PM
One shot a Postgres clone in Zig. No mistakes.
"the average app can get away with postgres" the average app can get away with a single json file on disk yet for some reason nobody argues in favor of that, interesting
November 2, 2026 at 4:34 PM
"the average app can get away with postgres" the average app can get away with a single json file on disk yet for some reason nobody argues in favor of that, interesting
they call it postgres because you're posting
November 2, 2026 at 3:03 AM
they call it postgres because you're posting
Use FlubDB. BonkDB can do it. WhamDB is 1087x faster than Postgres. SlopDB has what you need. Use SlopDB in prod. Everything is stored in SlopDB. npm install SlopDB.
there is no reason to make a new database. postgres can do it. if you think postgres can't do it, you just haven't found the right way to enable it in pg_settings yet
November 2, 2026 at 3:27 AM
Use FlubDB. BonkDB can do it. WhamDB is 1087x faster than Postgres. SlopDB has what you need. Use SlopDB in prod. Everything is stored in SlopDB. npm install SlopDB.
There are three, maybe four databases worth bothering with: Postgres if you need a server, SQLite if you don’t, DuckDB if you need OLAP, maybe Clickhouse if you need server OLAP (I remain unconvinced) and Excel.
"Nobody got fired for choosing PostgreSQL"
November 2, 2026 at 12:44 PM
There are three, maybe four databases worth bothering with: Postgres if you need a server, SQLite if you don’t, DuckDB if you need OLAP, maybe Clickhouse if you need server OLAP (I remain unconvinced) and Excel.
postgres is not fine, actually, and the fact that we've been unable to produce anything better should embarrass our profession
November 2, 2026 at 4:29 PM
postgres is not fine, actually, and the fact that we've been unable to produce anything better should embarrass our profession
Concur. Just use Postgres.
it's funny that this is like, Veteran Wisdom, but as a general rule postgres is fine, and if you are using something that is not postgres you had better have a good reason why it's not postgres.
sqlite is fine as long as you know it's small
sqlite is fine as long as you know it's small
there is no reason to make a new database. postgres can do it. if you think postgres can't do it, you just haven't found the right way to enable it in pg_settings yet
November 2, 2026 at 2:06 PM
Concur. Just use Postgres.
v0 of anything can & should be implemented in postgres (sqlite if it's local). it's fine to pick something else later once you actually know what your workload is. but you can probably just keep using pg
November 2, 2026 at 3:40 AM
v0 of anything can & should be implemented in postgres (sqlite if it's local). it's fine to pick something else later once you actually know what your workload is. but you can probably just keep using pg
ok but I have this idea that I've been meaning to try on postgres
November 2, 2026 at 12:56 PM
ok but I have this idea that I've been meaning to try on postgres
I will probably adopt postgres in a moment of weakness one day though
November 2, 2026 at 9:32 PM
I will probably adopt postgres in a moment of weakness one day though
idgaf if you run OLAP workloads on postgres but please do not run them on my OLTP database
no not even the readers, unless you are Very Clever about MVCC
no not even the readers, unless you are Very Clever about MVCC
November 2, 2026 at 6:25 AM
idgaf if you run OLAP workloads on postgres but please do not run them on my OLTP database
no not even the readers, unless you are Very Clever about MVCC
no not even the readers, unless you are Very Clever about MVCC
The next PGKC in person event will be one week from today on Monday, November 9th! Join them for “Postgres: Take a Hint” with Dan Gras and Elizabeth Christensen!
www.meetup.com/kansas-city-...
#PostgreSQL
www.meetup.com/kansas-city-...
#PostgreSQL
Postgres: Take a Hint, Mon, Nov 9, 2026, 5:00 PM | Meetup
Let's meet and talk about using query hints in Postgres. There's a 3rd party extension to do this called pg_hint_plan and a new feature coming in Postgres 19 to add query p
www.meetup.com
November 2, 2026 at 6:20 PM
The next PGKC in person event will be one week from today on Monday, November 9th! Join them for “Postgres: Take a Hint” with Dan Gras and Elizabeth Christensen!
www.meetup.com/kansas-city-...
#PostgreSQL
www.meetup.com/kansas-city-...
#PostgreSQL
you can't abuse sqlite to make a job queue. you can abuse postgres for this.
November 2, 2026 at 9:26 AM
you can't abuse sqlite to make a job queue. you can abuse postgres for this.
Oh I was being ironic; as far as I know, Postgres is still the right bet, but that won't stop folks from trying
November 2, 2026 at 6:47 PM
Oh I was being ironic; as far as I know, Postgres is still the right bet, but that won't stop folks from trying
October's @postgres.scot #meetup: @sqlliz.bsky.social on what's new in #PostgreSQL 18 & 19, plus a lightning talk on pg_lakekeeper. Next in #Edinburgh in November!
vyruss.org/blog/postgre...
#OpenSource #Scotland #Database #Postgres #ApacheIceberg #Lakekeeper
vyruss.org/blog/postgre...
#OpenSource #Scotland #Database #Postgres #ApacheIceberg #Lakekeeper
Postgres Edinburgh October 2026 Meetup Recap
A recap of our October meetup: Elizabeth Christensen of Snowflake on what is new in Postgres 18 and 19, including what did not make it into 19. Plus a short lightning talk from me on pg_lakekeeper.
vyruss.org
November 3, 2026 at 6:21 PM
October's @postgres.scot #meetup: @sqlliz.bsky.social on what's new in #PostgreSQL 18 & 19, plus a lightning talk on pg_lakekeeper. Next in #Edinburgh in November!
vyruss.org/blog/postgre...
#OpenSource #Scotland #Database #Postgres #ApacheIceberg #Lakekeeper
vyruss.org/blog/postgre...
#OpenSource #Scotland #Database #Postgres #ApacheIceberg #Lakekeeper
I have the opposite heuristic, somewhat. For most things, SQLite is fine. For the things that you need postgres for, you better be able to explain *precisely* why you need to stand it up, and if you can't, use SQLite instead. Anything less than that is negligence and vanity.
it's funny that this is like, Veteran Wisdom, but as a general rule postgres is fine, and if you are using something that is not postgres you had better have a good reason why it's not postgres.
sqlite is fine as long as you know it's small
sqlite is fine as long as you know it's small
there is no reason to make a new database. postgres can do it. if you think postgres can't do it, you just haven't found the right way to enable it in pg_settings yet
November 2, 2026 at 8:03 AM
I have the opposite heuristic, somewhat. For most things, SQLite is fine. For the things that you need postgres for, you better be able to explain *precisely* why you need to stand it up, and if you can't, use SQLite instead. Anything less than that is negligence and vanity.