It is with great pleasure that we announce the final program for PGConf Local: Seattle. The schedule is still being hammered out but we have finalized the content that will be presented. Please join us in celebrating Postgres in Seattle!

PostgresConf ran its first Silicon Valley conference on October 15th and 16th in conjunction with Silicon Valley Postgres. The two day conference was considered a “local” or development conference where our focus was introducing the PostgresConf experience to new attendees and partners with world class content. We believe we succeeded in that.

We brought new friends to the community with the addition of Yugabyte, Scalegrid, and AgensGraph. We also had old friends return with Pivotal, AWS, Microsoft, 2ndQuadrant, Timescale, Compose, and Nutanix.

This is the first conference we have organized where the attendance went up during the conference. All community conferences know the stress of waiting for people to register. We all register at the last possible moment but for attendance to increase as the conference is running was new for us. It added a new level of legitimacy to our purpose of:

Thank you to the attendees, supporters, and organizers for helping pull off yet another amazing event!

Seattle Postgres and People, Postgres, Data were present at the 20th Anniversary Event of LinuxFest Northwest this weekend! The “Fest” is a conference built around Free and Open Source Software, taking place in Bellingham, Washington. It is a true gathering of over 2000 Open Source practitioners. There was also a well attended Postgres Track and an “Ask the experts” panel.

Highlighted Find

Also at LinuxFest Northwest was YottaDB. YottaDB uses the PostgreSQL wire protocol to allow universal driver access to their in-memory transactional database. This has become a popular way to utilize the maturity of the PostgreSQL code base and reduce overhead in having to maintain a protocol and drivers.

Ecosystem Content

• What is high cardinality, and how do time-series databases like InfluxDB and TimescaleDB compare?

• 11 Things to Know about Databases and Postgres in Containers

• PostgreSQL security: a quick look at authentication best practices [Tutorial]

• Distributed PostgreSQL on a Google Spanner Like Architecture - Storage Layer

Requesting Feedback

We are looking for good dates to host PostgresConf Philly in July/August 2019 and we are actively reviewing new markets for other Postgres Conference events including Texas, Vancouver B.C., and Seattle. If you have feedback on opportunities in these areaa including dates, venues, or a desire to join the amazing People, Postgres, Data team, let us know at organizers@postgresconf.org.

 

Noteworthy Commits & Releases

The PostgreSQL git repo was largely bug fixes and updates the past couple of weeks but we have some great releases including migration tools and Distributed SQL:

 

• Outflux (Outflux -> TimescaleDB migration tool)

• Yugabyte v1.2.4 (Apr 02, 2019), Distributed SQL

• Postgres Checkup 1.0, Automate checking on Postgres health

• PgCLI v2.1.0, A feature-full command line client for Postgres

Join our community

• News and Announcements

Upcoming Events

• Postgres Ibiza

• PostgresConf Beijing

• PostgresConf Silicon Valley

• Silicon Valley Postgres Meetup

People, Postgres, Data and The World’s Database

 

The World’s Database celebrates all of Postgres, including whichever version, fork, or hybrid used to build yourself, your business, or your hobby. We have Open and Closed Source technologies. We have amazing extensions (TimescaleDB), unique implementations (Yugabyte), and respected forks to solve specific problems such as Greenplum, Azure, and Aurora. We have meetups where professionals can gather to collaborate and network in all major U.S. markets. Most importantly we are an inclusive community celebrating everything surrounding the maturity, extensibility, and growth of the Postgres ecosystem.

So let's point your Firefox, Google Chrome, or Safari app to this link right here and get your presentation submitted.

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.

• 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.

Join the fantastic and growing Postgres community in Cape Town, South Africa for a single day event on October 3rd, 2017! The event is being hosted by fellow Postgres advocates who travel from South Africa each year to attend our National Event in order to increase their knowledge of Postgres and be a part of the community. This year they are joining us and making a commitment to build out our International community and conferences!

• The CFP is open is open from now until August 25th. We will notify speakers by September 1st! Talks are subject to our presentation guidelines.

Local events are designed to bring comprehensive educational content and networking opportunities to the "local" Postgres community where the event is being held. They are perfect opportunities to show support for Postgres, find leads, and build relationships with other professionals and companies using and supporting Postgres.

That's right, folks; the time has come. 

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