3 ms·
The follower hole was a long running bug for us back when I was at Heroku, it existed for at least 5 years. In fact it'd become a bit of a joke so much so that
by craigkerstiens 9y ago
The follower hole was a long running bug for us back when I was at Heroku, it existed for at least 5 years. In fact it'd become a bit of a joke so much so that when we'd start our planning process each time (http://www.craigkerstiens.com/2013/03/13/planning-and-prioritizing/ http://www.craigkerstiens.com/2013/03/13/planning-and-priori...) we'd start by placing "fix the follower hole" in the high on effort and low on impact to use as an anchor for everything else.
Congrats to the team for digging into a hard problem which Daniel never solved ;), squashing it, and then the great write-up about it.
- kawsper 9y agoThanks for sharing that link, and your story about your time at Heroku, it is very inspiring. But I have one quesiton, who is Daniel? :)
- craigkerstiens 9y agoHa. Daniel was the first engineer hired on the Heroku Postgres team. He authored wal-e (https://github.com/wal-e/wal-e https://github.com/wal-e/wal-e) which is the foundation for much of the fork/follower functionality and thus the follower-hole itself. He's now running databases with me at Citus.
- keiko713 9y agoand my job here at Heroku Postgres is to delete Daniel’s code
- brianwawok 9y agoDestroying is so much more work than creating.