There are a couple big things that are probably useful context here. The first is the different between core team and committers. The core team is much more li

There are a couple big things that are probably useful context here. The first is the different between core team and committers. The core team is much more like a steering committee than anything else. The core team is responsible for various policy issues, coordinating broader release activities, and handling disciplinary issues. In contrast, committers are the ones that determine what code goes in and does not. The list of committers is about 30 people. And there are many people that work to contribute large pieces of code but not responsible for the final leg of committing. Edit: I've written a bit more before on all of the non-code bits of Postgres - http://www.craigkerstiens.com/2017/10/31/postgres-the-non-code-bits/ http://www.craigkerstiens.com/2017/10/31/postgres-the-non-co...