Hacking on PostgreSQL is hard
rhaas.blogspot.com
Hacking on PostgreSQL is hard
1–10 of 56 posts
Re: Hacking on PostgreSQL is hard
#2[deleted]
Re: Hacking on PostgreSQL is hard
#3through writing extensions luckily isn't
Re: Hacking on PostgreSQL is hard
#4through writing extensions luckily isn't
So is the path to create an extension and hope that someone with a deeper understanding can pull the main features into postgres major_version+1?
Re: Hacking on PostgreSQL is hard
#5through writing extensions luckily isn't
So is the path to create an extension and hope that someone with a deeper understanding can pull the main features into postgres major_version+1?
> deeper understanding can pull the main features into postgres major_version+1?
for a lot of stuff you don't need it, sometimes even don't want it
Re: Hacking on PostgreSQL is hard
#6Original submission:
https://news.ycombinator.com/item?id=40234398
Re: Hacking on PostgreSQL is hard
#7Original submission: https://news.ycombinator.com/item?id=40234398
OP was original submission—you can tell this because its ID is smaller.
Timestamps get relativized when we re-up a post [1]. That's an artifact of HN's re-upping system [2].
[1] https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...
[2] https://news.ycombinator.com/item?id=26998308
Sorry for the confusion—I know it's weird but the alternative turns out to be even more confusing and we've never figured out how to square that circle!
Re: Hacking on PostgreSQL is hard
#8The most enlightening part of the article was in the comments where it was observed that given the length of time Postgres has been going, the number of talented developers who have worked on the project there are no easy enhancements or fixes left, just hard knotty problems. (paraphrasing).
It's almost a mark of success of the project. There is obviously a lot of dedication too.
Re: Hacking on PostgreSQL is hard
#9[deleted]
Re: Hacking on PostgreSQL is hard
#10[deleted]
[deleted]