Postgres is still single-node-first, and while Citus exists I'm skeptical that it can ever become as easy to administer as a true HA-first datastore. For me the reason to use something like Cassandra or Kafka was never "big data" per se, it was having true master-master fault tolerance out of the box in a way that worked with everything.
Postgres is eating the database world
31–40 of 147 posts
Re: Postgres is eating the database world
#32I have a handful of sites I run on a VPS with a basic setup, including MySQL.
One thing I've always liked about MySQL is that it pretty much looks after itself, whereas with Postgres I've had issues before doing upgrades (this was with brew though) and I'm not clear on whether it looks after itself for vacuuming etc.
Should I just give it a go the next time I'm upgrading? It does seem like a tool I need to get familiar with.
Re: Postgres is eating the database world
#33Is there an extension that can make it compete with TigerBeetle for transaction processing speed?
Why downvoted? Genuine question.
Re: Postgres is eating the database world
#34Postgres is such a great tool. The feature I'd love to see added that has been kicking around the mailing list for ages now would be incremental view maintenance. Being able to keep moderately complex analysis workloads fresh in realtime would be such a boon.
Materialized views with pg_cron to refresh them? (Or even just cron and your usual interface, if you don't want to install something extra)
This solves the same problem, just not as well, the idea of an incrementaly maintained view is that only the update needs to be computed, so a count will increment or decrement as rows are inserted or deleted.
It means complex views that could take minutes or hours to calculate from scratch can be kept fresh in realtime.
Re: Postgres is eating the database world
#35Alright I'm convinced, I'm using postgres for my next project. Anyone have any experiences with it and Entity Framework Core?
[deleted]
Re: Postgres is eating the database world
#36I have a handful of sites I run on a VPS with a basic setup, including MySQL. One thing I've always liked about MySQL is that it pretty much looks after itself, whereas with Postgres I've had issues before doing upgrades (this was with brew though) and I'm not clear on whether it looks after itself for vacuuming etc. Should I just give it a go the next time I'm upgrading? It does seem like a tool I need to get famili…
The price is right and auto-vacuuming is a thing.
Re: Postgres is eating the database world
#37Postgres is still single-node-first, and while Citus exists I'm skeptical that it can ever become as easy to administer as a true HA-first datastore. For me the reason to use something like Cassandra or Kafka was never "big data" per se, it was having true master-master fault tolerance out of the box in a way that worked with everything.
That looks like apples vs oranges.
Re: Postgres is eating the database world
#38Postgres is such a great tool. The feature I'd love to see added that has been kicking around the mailing list for ages now would be incremental view maintenance. Being able to keep moderately complex analysis workloads fresh in realtime would be such a boon.
https://github.com/sraoss/pg_ivm does what you need
Re: Postgres is eating the database world
#39Postgres is such a great tool. The feature I'd love to see added that has been kicking around the mailing list for ages now would be incremental view maintenance. Being able to keep moderately complex analysis workloads fresh in realtime would be such a boon.
Materialized views with pg_cron to refresh them? (Or even just cron and your usual interface, if you don't want to install something extra)
Re: Postgres is eating the database world
#40Alright I'm convinced, I'm using postgres for my next project. Anyone have any experiences with it and Entity Framework Core?
I'm using EF Core with SQL Server and PostgreSQL for two different production projects; it works like a charm, and the performance is great.
All recent projects in my company are PostgreSQL based (> 2000 production applications), and we have far fewer troubles with PostgreSQL than with Oracle, not to mention the licensing.