developper39 42 minutes ago

Very usefull, and it is clear that the author knows what he is talking about. Nice intro to Pg18 too.

Reply View 0 replies
lysace 25 minutes ago

Insipid text.

Also: HN needs to upgrade it's bot upvoting detection tech. This is embarrassing.

Reply View 0 replies
alberth an hour ago

Odd that OLTP wasn’t mentioned in the article.

Postgres an an OLTP databases, which are designed for write heavy workloads.

While that being said, I agree most people have read-heavy needs.

Reply View 1 reply
  • da_chicken 15 minutes ago

    I disagree. I think the only people that have read-heavy needs are big data and data warehouses. AI being hot right now doesn't mean big data is the only game in town.

    Most applications are used operationally or have a mix of read and write. Even on applications where the user can only consume content present there, there is often more than enough data capture just tracking page history to be relatively write heavy.

    Reply View 0 replies
jagged-chisel 3 minutes ago

> When someone asks about [database] tuning, I always say “it depends”.

Indeed. On your schema. On your usage. On your app. On your users.

Reply View 0 replies