>
"- Not distributable"
This is something that's actively being worked on. It's also useful to look at the systems that
are more easily distributable, and compare other features they posses with Postgres. Aphyr has provided a wonderful service with Jepsen showing just how difficult correctness in general (with and without the added complexity of distributability) actually is.
- "Poor resiliency" Do you mean something by this beyond as an aspect of distributability?
- "Hard to upgrade" The story here has been much improved, both with pg_upgrade and though features such as logical replication.
- "Schemas remains at postgres core" Would you elaborate what you mean by this?
I would also ask you to elaborate what you mean by "However it's also one of the most (if not the most) bloated." In terms of binary size? Feature set? Actual on-disk data representation? If so, what are you comparing it to?
Similarly, "It feels like things haven't changed that much since the 90's.": Having used Postgres over the years, I can certainly say that things have become much easier. What in particular are you thinking of?
I also struggle to square what appears to be complaints of capability while also expressing frustration with "postgres bloat and overall complexity of the system." As with all things, there are tradeoffs and resource limitations. What would you in particular are you looking for? And given the nature of Postgres as an open source project, what are you doing to ensure that those features you desire are being worked on? There are plenty of developers and organizations that are willing to work on bespoke features given the appropriate support.
Jepsen: https://jepsen.io
- "Poor resiliency" Do you mean something by this beyond as an aspect of distributability?
- "Hard to upgrade" The story here has been much improved, both with pg_upgrade and though features such as logical replication.
- "Schemas remains at postgres core" Would you elaborate what you mean by this?
I would also ask you to elaborate what you mean by "However it's also one of the most (if not the most) bloated." In terms of binary size? Feature set? Actual on-disk data representation? If so, what are you comparing it to?
Similarly, "It feels like things haven't changed that much since the 90's.": Having used Postgres over the years, I can certainly say that things have become much easier. What in particular are you thinking of?
I also struggle to square what appears to be complaints of capability while also expressing frustration with "postgres bloat and overall complexity of the system." As with all things, there are tradeoffs and resource limitations. What would you in particular are you looking for? And given the nature of Postgres as an open source project, what are you doing to ensure that those features you desire are being worked on? There are plenty of developers and organizations that are willing to work on bespoke features given the appropriate support.
Jepsen: https://jepsen.io