3 ms·
When will PG finally start using tasks instead of superheavyweight threads? When will they automatically precompile/hash statements to avoid reparsing? And when
by 2mm3mm3 3y ago
When will PG finally start using tasks instead of superheavyweight threads? When will they automatically precompile/hash statements to avoid reparsing? And when materialized views will be automatically updated? Where is an alternative to SQL Server Always On Availability Group released >10 years ago? PostgreSQL is the only database where guys recommend you to configure a separate connection pooler, because their database is unable to handle even mid. size number of connections.
- fooododododo 3y agoSeems like a rant rather than a comment to the post? Timescale has continuous aggregates that might be interesting, writing a table built by a trigger isn't hard, and some might say having a separate connection pooler is a feature rather than a bug... Idk enough about SQL server for the group part.
- kiwicopple 3y agoit's a great list. No database is perfect, and this is a good set of features that are missing from Postgres that said, the flexibility/extensibility of Postgres still makes it a great choice. You could easily point at other databases and produce a list similar (or longer) than this.
- Yasuraka 3y agoI'll take vertical sharding until no longer possible and then dropping all further requests over touching Always On Availability Groups ever again
- Yasuraka 3y agovertical scaling*
- anarazel 3y agoWhen will you contribute?
- Too 3y agoThe way Postgres is worshiped as The Holy Grail here on HN, some reality check on where it is lacking should be ok to rant about, just to balance the discussion, with no expectations on fixing it. One can also choose a different tool. In this thread, it’s not exactly on topic though.
- paulddraper 3y agolol, salty