Congratulations

Henrietta Dombrovskaya, Diversity, Equity, and Inclusion member for PostgresConf as well as Chicago Postgresql organizer nominated for Technologist of the Year!

Career Opportunity

A large, well known media company is seeking a Senior Level PostgreSQL Engineer and Architect. This is an on-site engagement, however the company is known to be lifestyle friendly with reasonable working hours, good pay, and benefits. Specific talents requested are the ability to mentor. The location is Seattle, WA. If you are interested in this position please contact randy@neuringerco.com with your resume.

Great content

• Doubling the Sorting Speed of Postgres Network Types with Abbreviated Keys

• Automatically updating Materialized Views

• OrderedAppend: An optimization for range partitioning

Extension Highlight

We wanted to highlight some of the fantastic work that is being done by the ecosystem with Postgres Extensions. Although the base of Postgres is the amazing and extensible PostgreSQL, a lot of users don’t realize that Postgres has the feature they are looking for, if only they were to look to the ecosystem.

Notable Extensions:

• pgaudit : The goal of pgAudit is to provide PostgreSQL users with the capability to produce audit logs often required to comply with government, financial, or ISO certifications.

• pg_credereum : pg_credereum is a PostgreSQL extension that provides a cryptographically verifiable audit capability for a PostgreSQL database, bringing some properties of blockchain to relational DBMS.

• H3-pg : PostgreSQL bindings for H3, a hierarchical hexagonal geospatial indexing system.

Postgres can do what?

There are a ton of Postgres compatible features out there. Some of them are overlooked core features and some of them require installing a different version of Postgres. Here are a few examples:

• TimescaleDB: Time series data management with Postgres

• YugabyteDB: Globally Distributed database with PostgreSQL compatibility

• Postgres-XL: Horizontally partitioned PostgreSQL

• Agensgraph: Graph capabilities with Postgres

• PG-Strom: GPU accelerated extension for Postgres 

Upcoming Education and Networking opportunities:

• PostgresConf Silicon Valley

• PostgresConf South Africa

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!

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.

Community,

PGConf US and Austin PUG organized a PGConf Mini last night. It was three presentations over the evening. We had good attendance and excellent community participation. The highlight of the evening was PGConf US Co-Chair Jim Molgendski's presentation, "Top 10 Mistakes When Migrating from Oracle to PostgreSQL".

We tried something new this time around. We utilized Twitter's Periscope capability to live stream his presentation. It wasn't perfect but it was our first time and we are looking forward to utilizing the platform more in the future.

Click here to watch "To Mistakes When Migrating From Oracle to PostgreSQL", and then submit a presentation to one of our upcoming conferences:

• PGConf US Local: Philly
• PGConf US Local: Seattle

Like most conference organizers we are learning to adapt to the new world; a world where physical events are no longer viable (at least in 2020). A world where people are genuinely and realistically concerned that an in-person event would increase their chances of receiving or spreading a life threatening virus.

The question is: Are in-person events a thing of the past?

The answer to that question is a difficult one. Our friends at O'reilly and Associates have permanently canceled their in person events. Our friends in Europe recently canceled the well respected PgConf.EU and Ibiza. We had to cancel our 2020 marque event in NYC in March and our upcoming Silicon Valley conference. The local community organizer website Meetup.com has even modified their capabilities to allow for online meetups. 

Humans in general seek out fellow human contact. That contact is usually of reasonably like minded individuals or at least mutual interests. This is why events like Postgres Conference are successful, because irrespective of any personal beliefs we are all there to learn and enjoy fellow Postgres professionals. But are virtual meetups and conferences going to be enough to satisfy that connection or are people going to demand a return to a historical norm?

Challenges

Even before COVID-19, in-person events came with challenges that put significant pressure on volunteers. Between cultural communication differences, having an independent Code of Conduct committee, pricing, economies of scale, partner demands, and now social distancing, conferences are now going to be more complicated than ever. A room that once could comfortably seat 100 can now only properly sit 30. An exhibit hall is likely out of the question and one-on-one mentoring and networking are likely not going to be viable.  How do we work around these limitations? Is it worth it? Are the people in our community even interested anymore or is it time to accept a new norm?

Opportunity

Without question this is a time of reflection, continued development of relationships, and looking into the magic 8-ball; a continual asking of questions to find the right path forward. The pandemic is a tough foe but true leaders are looking forward and trying to find ways to continue to serve. For that to be successful we need your help. We have put together a poll (that can be found here) to gain insight into what opportunities we may be able to pursue in the future. Please take a couple minutes and help shape the future of Open Source events. 

As a closing, we are actively moving forward with Digital Events across the globe and have an unending Call for Presentations open for Webinars. If you have any feedback or brilliant ideas, please send them to us via organizers@postgresconf.org.

Blatant Poll Link 

• https://www.pgconf.us/conferences/Philly2017

• https://www.pgconf.us/conferences/Philly2017/sponsors

Invisible Disease Awareness

“According to the Disabled World website, an estimated 10% of the U.S. population has what could be considered an ‘invisible’ disease, defined as a health condition that causes significant impairment and undermines the overall quality of life but does not outwardly manifest itself in ways that are apparent to others.” [1]

While normally our focus is Postgres, we wanted to take a moment to bring attention to the People side of People, Postgres, Data. May is mental health and Ehlers-Danlos awareness month. Ehlers-Danlos Syndrome (EDS) is a rare condition that affects the collagen throughout the entire body, resulting in dislocations, subluxations, lack of joint stability and support, tendinosis, and debilitating pain. There is no cure and the symptoms are life long.

In 2020, PostgresWarrior (AKA Amanda Nystrom) was diagnosed with Hypermobile EDS and Fibromyalgia. She is an instrumental and invaluable member of the People, Postgres, Data community. She has driven us forward in ways that so many of us never see and yet require to succeed. Many of our community are affected by invisible diseases - let's take a moment to appreciate what they accomplish and fight for in Postgres/Open Source.

Upcoming webinars | RSVP here

• May 25, 1pm ET: Creating a Resilient PostgreSQL Cluster with Kubegres

• June 15, 1pm ET: When it All Goes Wrong - Incident Response in Large Postgres Databases

• June 23, 1pm ET: Making Postgres Fly on Kubernetes

• June 29, 1pm ET: Implementing Cluster File Encryption in Postgres

Community Chat

Our Discord Channel has 2000 community members waiting to participate in your Postgres success. Join us today with a community that has rule #1 of: Be Nice.

Podcasts

• Building Your Data Warehouse On Top Of PostgreSQL - Episode 186
• More than a Refresh: Stephanie Kirmer, Data Scientist for Saturn Cloud

1. https://www.socialworktoday.com/archive/072417p32.shtml

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