Improving PostgreSQL: How to Overcome the Tough Challenges

Posted by franckpachot on Wednesday October 04, 2023 @12:06PM
from the yugabyte.com dept.

https://www.yugabyte.com/blog/improve-postgresql/

( 6 comments | 14 points | on HN )

Re:Improving PostgreSQL: How to Overcome the Tough Challenges by proleisuretour on Wednesday October 04, 2023 @12:26PM (#37767521)

Definitely agree with Branson's top 10 of challenges with PostgreSQL, especially #3: "Inefficient Replication That Spreads Corruption". Postgres WAL entries are always the bottleneck of a replication stream.

[ Parent | on HN ]

Re:Improving PostgreSQL: How to Overcome the Tough Challenges by franckpachot on Wednesday October 04, 2023 @12:27PM (#37767550)

Interesting, that's the one I don't really agree with. Bottleneck, yes, because it is a monolithic stream for the whole database. But corruption?

[ Parent | on HN ]

Re:Improving PostgreSQL: How to Overcome the Tough Challenges by 3littlefish on Wednesday October 04, 2023 @12:14PM (#37767311)

Does Yugabyte actually contribute to Postgres or just use their code?

[ Parent | on HN ]

Re:Improving PostgreSQL: How to Overcome the Tough Challenges by franckpachot on Wednesday October 04, 2023 @12:18PM (#37767381)

Yes, everything Yugabyte does is open source

[ Parent | on HN ]

Re:Improving PostgreSQL: How to Overcome the Tough Challenges by mattashii on Wednesday October 04, 2023 @06:40PM (#37772761)

Open sourcing the changes doesn't mean contributing back to PostgreSQL: Someone has to put in effort to push changes into upstream PostgreSQL, and if it's not Yugabyte, then IMO they're not contributing back.

[ Parent | on HN ]

Re:Improving PostgreSQL: How to Overcome the Tough Challenges by maverick894 on Wednesday October 04, 2023 @01:02PM (#37768166)

definitely seen issues in #1 with 32-bit transaction ID and also the problems with connections in PG, but we can sort of manage around these.

[ Parent | on HN ]