Joshua D. Drake Blog Posts

• I must care about the content.
• I must deliver what I say I will deliver.
• I must be honest with the audience about my level of experience in the subject.
• I must be honest about my opinions on the subject.
• I must be a genuine version of me, minus the swearing.”

Disclaimer: I am writing this opinion as a frequent presenter, not as the Co-Chair of the most electrifying Postgres Conference in the world.

On occasion, professional developers will drop into the Postgresql.org mailing lists, meetups, and conferences to ask the question, “Why isn’t PostgreSQL development on Github?” In an effort to see if the demand was really there and not just anecdotal we ran a poll/survey over several social media platforms that asked a simple question:

Should PostgreSQL development move to Github?

• Yes
• No
• No, but to something like Gitlab would be good

We received well over 300 responses and the majority (75%+) chose a move to Github or to something like Github. This was an unscientific poll but it does point out a few interesting topics for consideration:

1. We need to recognize that the current contribution model does work for existing contributors. We need to have an honest discussion about what that means for the project as contributors age, change employment, and mature in their skill set, etc..
2. Of the people that argued in comments against the move to a service, only one is a current contributor to PostgreSQL.org core code. The rest were former code contributors or those who contribute in other ways (Advocacy, System administration, etc.).
3. Would a move to Github or similar option produce a higher rate of contribution?

This poll does not answer point #3; it only provides a data point that people may desire a modern collaboration platform. The key takeaway from the conversation about migrating to Github or similar service is the future generation of developers use technology such as Slack and Microsoft Teams. They expect a bug/issue tracker. They demand simplicity in collaboration and most importantly they will run a cost->benefit analysis to determine if the effort to contribute is a net positive.

It should also be considered that this is not just individual potential contributors. There are many corporations big and small that rely on the success of PostgreSQL. Those corporations will not contribute as much directly to PostgreSQL if the cost to benefit analysis is a net negative. They will instead contribute through other more productive means that produce a net positive when the cost->benefit analysis is run. A good example of this analysis is the proliferation of external projects such as pg_auto_failover, patroni and lack of direct contribution from innovative extension based companies.

Do we need a culture shift within PostgreSQL?

There are those within the Postgresql.org community that would suggest that we do not need a culture shift within PostgreSQL but that does not take into account the very clear market dynamics that are driving the growth of PostgreSQL, Postgres, and the global ecosystem. It is true that 20 years of hard work by Postgresql.org started the growth and it is also true that the majority of growth in the ecosystem and community is from products such as Greenplum, Aurora, Azure, and Timescale. The growth in the ecosystem is from the professional community and that ecosystem will always perform a cost to benefit analysis before contributing.

It is not that we should create radical rifts or disrupt our culture. It is to say that we must evolve and shift our community thinking. We need to be able to consider the big picture. A discussion should never start as an opposition to change. The idea of change should be an open discussion about possibility and vision. It should always include whether the change is a good idea and it should always avoid visceral reactions of, "works for me,” “no,” or “we tried that 15 years ago." Those reactions are immature and lacking in the very thing the community needs to continue to grow: positivity, inclusion, vision, and inspiration.

• Mastering PostgreSQL Administration

• Securing Data in a Multi-Platform Data Lake

• Personal Time Management

• Contributing to PostgreSQL

After National 2017, the PGConf US team decided to take a long hard road to bring the best in educational content and advocacy to the entire Postgres ecosystem. Today, we welcome 2ndQuadrant as a Platinum sponsor and thank them for helping us with our year over year projects.

Other PGConf US news:

With more than 200 events submitted and approximately 80 slots to be filled, this has been the most difficult schedule to arrange in the history of PostgresConf. By far, the majority of content received we wanted to include in the schedule. It is that level of community support that we work so hard to achieve and we are thankful to the community for supporting PostgresConf. There is no doubt that the number one hurdle the community must overcome is effective access to education on Postgres. The US 2018 event achieves this with two full days of training and three full days of breakout sessions, including the Regulated Industry Summit and Greenplum Summit.

See something you like? Then it is time to buy those tickets!

• Friday, September 29, 2017: Trainings

Mastering Postgres Administration: Bruce Momjian

Postgres Performance and Maintenance: Joshua D. Drake 

• Saturday, September 30, 2017: Breakout Sessions (To be announced)

People, Postgres, Data,

Due to the health risks and travel restrictions created by the Coronavirus we unfortunately have to cancel Postgres Conference 2020 which was to be held at the Marriott Marquis on March 23rd, 2020 thru March 27th, 2020.

We want to thank all of our attendees, partners and volunteers for all the hard work we all put in to try and pull this event off. Sadly, the stars were not aligned this year. We now focus our efforts on Postgres Conference Silicon Valley 2020 and our Digital Events. 

Thank you all for your patience and support,

Postgres Conference Chairs

The PostgresConf team wanted to provide some information on the performance of PostgresConf US 2018 and events over the past year, as well as potentially answer some pending questions. Ultimately our goals are about people, which is why our motto is, "People, Postgres, Data." With each event we hold, each talk we accept, and how we train our volunteers, we make sure people (the benefit for and to), postgres, and data are considered and included. If there is no benefit or consideration to the growth of people, it is not an option.

• Philadelphia 
• Ohio (in combination with Ohio Linux Fest) 
• South Africa 
• Seattle 
• Austin 
• Jersey City (PostgresConf US 2018) 
• Nepal 

PostgresConf US 2018

Logistics

• Days: 5, 2 for training, 3 for Breakout sessions and summits
• Official Attendance #: 601
• Content: Over 207 sessions submitted
• Sessions: Over 108 sessions provided 

Partner Support (Sponsors): 28

Diversity

Professional Growth

We held a Career and Talent Fair. A dozen companies were present to connect with potential employees.

We also held a surprisingly well attended speed mentoring session for potential employees (Especially helpful for many of the WWC) on resumes and interview practices.

Leadership

This year saw the continued elevation of our primary leadership: Viral Shah, Lloyd Albin, Amanda Nystrom, and Debra Cerda. They continued to increase their presence and responsibility within the conference and dedicated hundreds of hours voluntarily to the growth of people. Our international members have also increased their leadership roles with our on-the-ground teams in South Africa and China.

Summits

We had our standard Regulated Industry Summit but also a Greenplum Summit. As I am sure you are aware Greenplum is an Open Source, Postgres based MPP database. They were by far the most popular booth in the entire conference and their summit was very well attended. The relationship with Pivotal and the success of the Greenplum Summit allowed us to learn new ways to bring together the entire Postgres Ecosystem. We expect to run a minimum of 3 more summits at PostgresConf US 2019.

Contribution

We were able to have several excellent (and long) meetings with leaders of Pivotal, Microsoft, Google, and Amazon on how they can begin contributing more back to Postgresql.org. All of them expressed a deep drive to contribute and a desire to learn more about the core community. Of particular note is Google, who would like to contribute the following back to the community:

https://github.com/google/pg_page_verification

We discussed with them the process and various changes they would need to make (license and code style, etc.). We also educated them on the PostgreSQL.Org rigorous review process.

Microsoft is reviewing how they can contribute but they showed an interest in build farm nodes, professional technical writers to help with docs, and potentially code contribution to our Windows port.

International Collaboration

The Chinese Open Source Promotion Union launched the Chinese Postgres Association. We invited them to PostgresConf US and introduced them to the United States Community. We expect great things from the Chinese community in the future.

Future

As we continue to build up our on-the-ground teams, we will likely hold less events in the U.S. this year. We will instead be focused on a smaller number of events in the U.S. and adding events in China and Europe. We have had an amazing amount of support from the Chinese community and the current goal is 1000 attendees for that conference.

Our current plan of events for the U.S. are

• San Jose (October 2018) 
• Philadelphia 
• PostgresConf US (Manhattan) 

Future International Events

• October 2018. 
• Spring of 2019. 
• Spring of 2019. 

This may change as we are actively recruiting on-the-ground teams to help us grow the community.

Collaboration

Our goal is collaboration and growth with other PostgreSQL community and Ecosystem efforts. We want to allow each potential community member to find a home. A place that they feel positive about contributing to the community as a whole. As we continue to grow as a community, it is vital to recognize that each member has their own needs, desires, and return on investment requirement (professional or personal) that they are seeking.

Tidbits of note

• Pivotal went public during PostgresConf US 2018. 
• We (PostgreSQL and PostgresConf) were picked up by ZDNet during the conference
• Another flattering article about PostgreSQL

On DBEngines PostgreSQL is the 4th most popular database but the significance is that of the other 3, we are the only ones that are growing in popularity.