Live data from Hacker News

It's 2026, Just Use Postgres

tigerdata.com

131–140 of 349 posts

Re: It's 2026, Just Use Postgres

#131

Earlier quoted context omitted.

You exceeded the step of maxing out the best server you can buy?

HA is not about exceeding the limits of a server. Its about still serving traffic when that best server I bought goes offline (or has failed memory chip, or a disk or... ).

Replication?

Re: It's 2026, Just Use Postgres

#132
Only if DuckDB is an acceptable value of PostgreSQL. I agree that PostgreSQL has eaten many DB use-cases, but the breathless hype is becoming exhausting.

Look. In a PostgreSQL extension, I can't:

1. extend the SQL language with ergonomic syntax for my use-case,

2. teach the query planner to understand execution strategies that can't be made to look PostgreSQL's tuple-and-index execution model, or

3. extend the type system to plumb new kinds of metadata through the whole query and storage system via some extensible IR.

(Plus, embedded PostgreSQL still isn't a first class thing.)

Until PostgreSQL's extension mechanism is powerful enough for me to literally implement DuckDB as an extension, PostgreSQL is not a panacea. It's a good system, but nowhere near universal.

Now, once I can do DuckDB (including its language extensions) in PostgreSQL, and once I can use the thing as a library, let's talk.

(pg_duckdb doesn't count. It's a switch, not a unified engine.)

Re: It's 2026, Just Use Postgres

#133
post #56

Earlier quoted context omitted.

to be fair, Postgres cana basically do everything Mongo can and just as well.

Ok, I'm a little skeptical of that claim but let's grant it. I still don't think Postgres is going to do everything Kafka and Redis can do as well as Kafka or Redis.

pgmq gets very close for a lot of Kafka use cases

Re: It's 2026, Just Use Postgres

#134
Pinecone allows hybrid search, merging dense and sparse vector embeddings that Postgres can't do AFAIK. That results in ~10% worse retrieval scores which might be the difference between making it in the business or not.

Re: It's 2026, Just Use Postgres

#135

Gad, they sure like to say "BM25" over and over again. That's a near worthless approach to result ranking. Doing any halfway ok job requires much more tuned and/or more powerful approaches.

It's common to do a hybrid of BM25 with other fuzzy search or pgvector.

BM25 is quite bad and needs to be retrained for each corpus anew. SPLADEv2 is much better and there are even better sparse embeddings these days.

Re: It's 2026, Just Use Postgres

#136

I do agree, I don’t know why more people don’t just use Postgres. If I’m doing data exploration with lots of data (e.g., GIS, nD vectors), I’ll just spin up a Postgres.app on my macOS laptop, install what little I need, and it just works and is plenty fast for my needs. It’s a really great choice for a lot of domains. That being said, while I think Postgres is “the right tool for the job” in many cases, sometimes you…

Where I have used SQLite most successfully is really two use cases. First, I use it for data processing. Say I need to retrieve lots of data and transform it to a different setup. I could do that in something like Python but SQL is just more expressive for that and I can also create a new database, populate it with data I have, fetch new data, combine it together, export the update to a permanent data store (usually Postgres).

Second, when I need a local save file. Sometimes small local apps are better served by a save file and they save file might as well have an extensible format that I can update as I go. This is more rare but still can be useful.

The first use case is very powerful. A temporary SQL database that can be blown away with zero trace of it is great. And the ability to run complex queries on it can really help.

But 99% of the time I just use Postgres. It works, it has sane defaults, it is crazy extensible, and it has never not met my needs, unlike Oracle or MySQL.

Re: It's 2026, Just Use Postgres

#137

Earlier quoted context omitted.

I do it. The big problem for me from running DB on Btrfs is that when I delete large dirs or files (100GB+), it locks disk system, and Db basically stop responding on any queries. I am very surprised that FS which is considered prod grade having this issue..

Try XFS if you havn’t yet. Very solid and no such issues.

I haven't used XFS in almost two decades, does it have compression support in the same way? Also, does it do JBOD stuff? I know it's a bit of a different thing, but I really enjoy the pool many disks together part of Btrfs, although it has its limitations.

Re: It's 2026, Just Use Postgres

#138

Earlier quoted context omitted.

I do it. The big problem for me from running DB on Btrfs is that when I delete large dirs or files (100GB+), it locks disk system, and Db basically stop responding on any queries. I am very surprised that FS which is considered prod grade having this issue..

Try XFS if you havn’t yet. Very solid and no such issues.

No compression.

Re: It's 2026, Just Use Postgres

#139

Earlier quoted context omitted.

Is HN guidelines to flag AI content? I am unsure of how flagging for this is supposed to work on HN and have only ever used the flag feature for obvious spam or scams.

It might be wrong, but I have started flagging this shit daily. Garbage articles that waste my time as a person who comes on here to find good articles. I understand that reading the title and probably skimming the article makes it a good jumping off point for a comment thread. I do like the HN comments but I don't want it to be just some forum of curious tech folks, I want it to be a place I find interesting content…

I agree. It seems this is kind of a shelling point right now on HN and there isn't a clear guideline yet. I think your usage of flagging makes sense. Thanks

Re: It's 2026, Just Use Postgres

#140

Earlier quoted context omitted.

Try XFS if you havn’t yet. Very solid and no such issues.

I haven't used XFS in almost two decades, does it have compression support in the same way? Also, does it do JBOD stuff? I know it's a bit of a different thing, but I really enjoy the pool many disks together part of Btrfs, although it has its limitations.

XFS doesn't have inline compression, nor does it have volume management functionality. It's a nice filesystem (and it's very fast) but it's just a filesystem.
Post reply on HN