Joshua D. Drake Blog Posts

PgConf US 2017 has now completed. We had a record number of attendees, a record number of sponsors and a record number of talks. The conference rocked. It was only made possible by a team of highly talented and dedicated volunteers. Thank you to those volunteers.

As of this writing, we are no longer the largest PostgreSQL Conference in North America. We are the largest PostgreSQL Conference. mic drop

Members of the South African Community

We attribute our growth directly to our community. We believe that there is no better community than the PostgreSQL community. A welcoming, inclusive community that shares knowledge and a common goal: Make PostgreSQL the database you use. It is because of this common goal that not only does our conference succeed, but the majority of PostgreSQL events across the globe succeed as well. It is why over 60% of our attendees have been using PostgreSQL for less than 3 years. It is why sponsors such as Amazon Web Services, EnterpriseDB, OpenSCG, and 2ndQuadrant consistently support the conference. It is why a brand new community member flew last minute from Texas the night before the conference (more on this new community member later). It is why the South African community shows up, every year.

Thank you to our speakers

There are quite a few knobs that get turned to run a conference and although it is an amazing experience to be a part of, it takes an enormous amount of resources (financially and physically) to execute it in a manner that is beneficial to all parties.

We think we did a pretty good job this year. This is not a pat on the back; we have more work to do. We want speakers to have everything they need including scheduled mentor times for first time speakers. We want speaking at PgConf US to be a pleasant, fun, and growth opportunity.

Thank you to our sponsors

We want sponsors to get better visibility. This was the first time at our current location and the layout wasn't perfect. We want to have "sponsor training." The PostgreSQL community is different than many, and sponsors (especially those that are relatively new to the community) should be able to leverage the expertise of the organizers to learn how best to work within the community. This would allow them to generate the business that makes it worth it for them to continue to sponsor.

We want coffee in the morning. Yes, the Chairs felt that coffee in the morning wasn't a requirement. Yes, the Chairs failed in a glorious fashion. We listen, we learn. There will be coffee in the morning at the next PgConf National.

There is more but that will wait for another day.

tl;dr; It is with sincerest hearts that the Chairs, Organizers, and Volunteers thank the community for supporting our efforts to bring the best PostgreSQL Conference experience possible.

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.

• Amazon
• Pivotal
• 2ndQuadrant
• Microsoft
• Timescale
• HighGo
• Data Dog
• Fivetran
• BlueTalon
• Goldman Sachs
• forhims
• Immuta

PGConf US in partnership with SeaPug is pleased to announce that the call for papers for PostgreSQL Conference US Local: Seattle is now open. 

National Diamond Sponsor

National Platinum Sponsor

Breakdown of the Conference Layout: 

• August 11th: Training
• August 12th: Breakout Sessions 

Attendees of PgConf.US , if you haven't gotten your hotel room booked, now is the time! Our block ends on March 6th. Point your browser over here and book that room. While you wait for your email confirmation from the Westin, you can take some time to review the following talk from PgConf US 2015, ToroDB: a new, open-source, document-oriented, JSON database, built on Postgres.

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

 

Following on the success of PostgresConf 2018, 2019 will include five days with added training and partner summits.

 

March 18th and 19th will have immersive training. Instructors are encouraged to submit half and full day material for consideration. The preferred topics are centered around Postgres but anything People, Postgres, or Data related will be considered.

Monday, March 18th through Friday, March 22nd will host several partner summits, including popular and upcoming topics within the Postgres community and the annually hosted Regulated Industry Summit. Break out sessions will be held from Wednesday - Friday.

In addition to the partner summits, PostgresConf 2019 will offer multiple program tracks with Postgres related topics including (but not limited to): 

• Postgres Internals
• Postgres Administration
• Operations and Development
• Data
• Cloud
• Database Security and Compliance
• Use Cases
• Regulated Industries
• Telecommunications
• Healthcare and life sciences
• Railroad, airline and pipeline transportation
• Oil and gas
• Electric power and transmission
• Financial services and trading 

PostgresConf is a global nonprofit conference series with a focus on growing community through increased awareness and education of Postgres and related technologies. PostgresConf is known for its highly attended national conference with the mission of:

• Friday, November 3, 2017: Half-day Trainings with Postgres experts
• Saturday, November 4, 2017: Breakout Sessions (lunch and coffee break provided)

PGConf US, in partnership with Ohio Linux Fest, is pleased to announce the schedule PGConf Local: Ohio is now available.

• Friday, September 29, 2017: Training. Registration for the PGConf Ohio trainings is open now.

Mastering Postgres Administration: Bruce Momjian