2 ms·
This is fixed in YugabyteDB that reuses the PostgreSQL query layer source code but uses it's own storage: https://www.yugabyte.com/blog/improve-postgresql/ http
by ddorian43 2y ago
This is fixed in YugabyteDB that reuses the PostgreSQL query layer source code but uses it's own storage: https://www.yugabyte.com/blog/improve-postgresql/ https://www.yugabyte.com/blog/improve-postgresql/ (other issues too like XID wraparound etc).
It's also apache2 license.
- knowitnone 2y agoThanks for pointing out Yugabyte. I did a search for performance comparisons and there seems (seemed?) to be some performance issues at least back in 2023 https://github.com/yugabyte/yugabyte-db/issues/10108 https://github.com/yugabyte/yugabyte-db/issues/10108 hopeful performance has improved since
- ddorian43 2y agoYes, performance is much better. But it's a bit apples to oranges comparisons because of distributed/sharding nature (example with bitmap scans https://www.yugabyte.com/blog/bitmap-scans-on-distributed-postgresql/ https://www.yugabyte.com/blog/bitmap-scans-on-distributed-po...), and always synchronous replication (https://www.yugabyte.com/blog/yugabytedb-resiliency-vs-postgresql-ha-solutions/ https://www.yugabyte.com/blog/yugabytedb-resiliency-vs-postg...).