Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

It's 2026, Just Use Postgres

tigerdata.com

Post reply on HN
Print view View original

21–30 of 349 posts

Re: It's 2026, Just Use Postgres

#21

Post by WorkerBee28474 »

yalldidwhat wrote: post #10
antirez wrote: post #4

The point of Redis is data structures and algorithmic complexity of operations. If you use Redis well, you can't replace it with PostgreSQL. But I bet you can't replace memcached either for serious use cases.

Did someone really downvote the creator of Redis ?

IIRC there was a pre-edit version with snark.

Re: It's 2026, Just Use Postgres

#22

Post by sailfast »

Love the sentiment! And I'm a user - but what about aggregations? Elasticsearch offers a ton of aggregates out of the box for "free" completely configurable by query string.

Tiger Data offers continuous aggs via hypertable but they need to be configured quite granularly and they're not super flexible. How are you all thinking about that when it comes to postgres and aggregations?

Re: It's 2026, Just Use Postgres

#23

Post by oldestofsports »

Caching is mentioned in the article: What do you guys feel about using PostgreSQL for caching instead of Redis?

Redis is many times faster, so much that it doesn't seem comparable to me.

A lot of data you can get away with just caching in-mem on each node, but when you have many nodes there are valid cases where you really want that distributed cache.

Re: It's 2026, Just Use Postgres

#24

Post by zzzeek »

Lots of familiar things here except for this UNLOGGED table as a cache thing. That's totally new to me. Has someone benched this approach against memcached and redis ? I'm extremely skeptical PGs query / protocol overheads are going to be competitive with memcached, but I'm making this up and have nothing to back it up.

Re: It's 2026, Just Use Postgres

#25

Post by evil-olive »

yalldidwhat wrote: post #10
antirez wrote: post #4

The point of Redis is data structures and algorithmic complexity of operations. If you use Redis well, you can't replace it with PostgreSQL. But I bet you can't replace memcached either for serious use cases.

Did someone really downvote the creator of Redis ?

I was one of the downvoters, and at the time I downvoted it, it was a very different comment. this is the original (copied from another tab that I hadn't refreshed yet):

> Tell me you don't understand Redis point is data structures without telling me you don't understand Redis point is data structures.

regardless of the author, I think slop of that sort belongs on reddit, not HN.

Re: It's 2026, Just Use Postgres

#26

Post by tallytarik »

kibibu wrote: post #15

Blog posts, like academic papers, should have to divulge how AI has been used to write them.

Yes this is clearly verbatim output from an LLM.

But it's perfect HN bait, really. The title is spicy enough that folks will comment without reading the article (more so than usual), and so it survives a bit longer before being flagged as slop.

Re: It's 2026, Just Use Postgres

#27

Post by EvanAnderson »

lucas1068 wrote: post #8

I've found that Postgres consumes (by default) more disk than, for example, MySQL. And the difference is quite significant. That means more money that I have to pay every month. But, sure Postgres seems like I system that integrates a lot of subsystems, that adds a lot of complexity too. I'm just marking the bad points because you mention the good points in the post. You're also trying to sell you service, which is g…

Some people do Postgres on compressed ZFS volumes to great success.

Re: It's 2026, Just Use Postgres

#30

Post by cpursley »

malkosta wrote: post #11

Elixir + Postgres is the microservices killer...last time I saw VP try to convince a company with this stack to go microservices he was out in less than 6mo

This is the killer combo. Working on something now that uses pgmq + Elixir for DAG workflows: https://github.com/agoodway/pgflow
Post reply on HN