• Mastering PostgreSQL Administration

• Securing Data in a Multi-Platform Data Lake

• Personal Time Management

• Contributing to PostgreSQL

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.

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!

1. Mastering PostgreSQL Administration by Bruce Momjian
2. Migrating from Oracle to PostgreSQL by Jim Mlodgenski
3. Postgres Performance and Maintenance by Joshua (JD) Drake
4. Database Automation by Robert Bernier 

• PostgreSQL v10 an Amplified version of Postgres!
• Using Kubernetes/Docker/Helm to Deploy On-Demand PostgreSQL Streaming Replicas
• Postgres Window Magic
• BDR Around the globe

• Diamond: Amazon Web Services
• Platinum: Compose, OpenSCG, 2ndQuadrant
• Partner: Quest
• Supporter: Command Prompt
• Media: @amplifypostgres

Brass tacks

• Silicon Valley is selling tickets briskly, get yours today and join us at the largest gathering of Postgres leaders on the West Coast.

• South Africa is set to release their schedule shortly. Watch the site for opportunities in October.

• We have hinted at digital events in the past and they are in the final planning stages. Digital events will encompass best in class content from our community in the format of Webinars, Q&A sessions and Professional electronic training opportunities. Watch for more news on these unique opportunities as we get closer to Fall 2019.

Seasons

It is the middle of summer, and as Glenn Frey would say, “The Heat is on!” Summer is the time when everyone is busy, yet nobody is busy. You have a contract to execute but the signer is on vacation. You have a project to complete but your digital nomad developer took off for the beach. Suddenly even checks may be delayed because of a long weekend up in the mountains. It is also a time to catch up on the things that may have been overlooked. When the person driving your priorities is on vacation it is easier to step back and observe your purpose.

Introduction

At PostgresConf 2019 in Manhattan we organized a Diversity and Inclusion panel with the help of Plato. The panel was well attended, but not as much as we had hoped. This fact outlined that we had more work to do on expanding our leadership position within Diversity, Equity and Inclusion in the Professional Postgres community.

We take this topic very seriously and we would consider PostgresConf and our focus on People, Postgres, Data a success if the only outcome was for all to feel welcome and supported within our community. Thankfully we have organizers and volunteers who are passionate about this very topic.

We would like to introduce the PostgresConf and PgCentral Foundation DEI (Diversity, Equity and Inclusion) Work Group:

• Debra Cerda: DEI Organizer

• Henrietta Dombrovskaya: Contributor

• Ryan Lambert: Contributor

• Mara Lemagie: Contributor

• Vikki McCormick: Contributor

• Amanda Nystrom: Co-Chair Sponsor

Over the coming months we will be continuing to communicate our passion, our purpose, our action and our accomplishments in bringing true Diversity, Equity and Inclusion to our community.

“A genuine leader is not a searcher for consensus but a molder of consensus” -- Martin Luther King

PostgresConf Philly which is organized in conjunction with Philly Postgres sold out in July! A packed room, great content and glorious collaboration was available to all for free due to the generous support of the Wharton School for Business!

As we continue to build our professional relationships, connections with academia are going to be vital. Academia is one of the few spaces that Postgres has not been able to make assertive gains in adoption and it crucial to the long term vision of our community that Academia recognize and adopt Postgres as the World’s Database and a viable option for teaching the next generation of data experts.

International communication

As our community grows Internationally with strong ties to Asia, and countries in the Southern Hemisphere it becomes difficult to connect with those cultures using our normal nomenclature. In our last newsletter we used a quote meant to be a compliment and challenge to the Western communities to try new things. The quote was about pigs ears and how they are delicious. The quote was interpreted by some in the Asia community as negative.

While writing this newsletter, we had used a spelling variation for the term “Wowzers” which in American pop culture is meant to be an exclamation of amazement. However in other cultures it maintains a negative connotation causing us to change the term to Kapow. These communication challenges show us that we must be open and without pride in our communication. We must show patience and understanding with cultures that are not like ours and that the communities that are able to achieve this will lead the future of Open Source and Postgres.

“Every human is like all other humans, some other humans, and no other human” — Clyde Kluckhon

PostgresConf US 2018 is in 9 days. Here is the obligatory "Buy your tickets" reminder! If you look around (a Google search of Gold sponsor Google Cloud is a good place to start) you will find a lot of discount codes.

In 2017 we launched a community wide effort to better recognize contributors for not only the conference but the wider Postgres Community. We continued this effort in 2018 and are pleased to have many speaker profiles available, with more being published every day:

• Les McMonagle
• Malcolm McLean
• Elizabeth Zalman
• Hubert Zhang of Pivotal
• Baron Schwartz
• Jignesh Shah
• Tim Gorman
• Tom Limoncelli