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

We are pleased to announce that Early Bird tickets to Postgres Conference 2019 are now available. Whether you are seeking a world class big data and analytics learning opportunity from the Greenplum Summit, a deep dive from the Google Cloud Summit, Regulated Industry Information from the Regulated Industry track, or a dizzying amount of learning opportunities from over 100 breakout sessions, PostgresConf 2019 is the show not to miss! Oh, and did we mention there will be training options as well?

Register here:

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

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 the pending GA release of Star Link, more cities adopting municipal WIFI, and the growth of remote work due to the pandemic, one would assume that cell phone providers would be falling hand over fist to provide quality services at a quality price. Unfortunately this is not the case and it is hurting the future of our workforce.

Carriers currently think that 30GB of Hotspot data is enough for the average digital nomad. While that may have been the case previously, it isn’t any longer. There is a hundreds-of-thousands-strong workforce specializing in Information Technology, Digital Design, Web Development, and other creative industries. They are living, working and adventuring in RVs, Sprinters, Skooolies (pictured), and other vehicle dwelling options. This community is nomadic by design and should not be artificially limited by technology. 

Why is it that we are being charged so much money for so little? Outside of two providers announcing rural initiatives, we are still acting like data needs are small and that they come at a quality price. Data is ubiquitous; it is the new water (for getting work done). In the new economy workers need faster, higher quality, and unlimited amounts of data to get their job done.

Where could you go and what could you experience if you weren’t tethered by the faux limitations of bandwidth?

Resources

• Community Chat 
• Upcoming Free Webinars
• Community Blogs

Featured Content

• Using PostgreSQL, PostGIS, and pgRouting for street sweeping
• Zheap dropped by EnterpriseDB: Cybertec takes lead
• Professionalism Matters

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

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

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.

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: