|
||
|
|
||
|
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:

Summer is officially over (although the calendar says otherwise), the kids are back in school, the last three-day camping weekend of the season has passed, and we are staring right at PostgresConf Silicon Valley starting September 18th! Registrations for this fantastic event have already exceeded 2018 numbers and our training day is showing great success.
Conferences

Register Today for API World 2019 and Save $200!
The API World team has offered us 25 free OPEN Passes and discounted PRO Passes to API World 2019 so our members can attend the event.
API World (October 8–10, San Jose Convention Center) is the world’s largest API & Microservices conference and expo with 3,500+ attendees, 60+ exhibitors, and 10+ tracks covering API Lifecycle Management, API Innovations, Microservices, Containers, Kubernetes, and more. 140+ speakers include leaders from Intuit, US Bank, IBM, Okta, Capital One, Box, Kong, GitHub, Comcast, Microsoft, Postman, Twillio, SendGrid, Oracle, Ford, UPS, Uber, Google, eBay and 100+ more.

GitLab Commit, our premier community event, brings together the GitLab community to connect, learn, and inspire. We want to make sure the NY tech community is well-represented at Commit so we are offering a HUGE discount to members of local tech community groups. You can use code 'COMMITCOMMUNITY102' to save 50%.
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?
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:
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.
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.
As one of the Founders of United States PostgreSQL, a former Director of Software in the Public Interest (one of the NPOs behind Postgresql.org), a former committer (web), former major contributor, President of the oldest PostgreSQL company still independent in North America, and the Founder of Postgres Conference (in the U.S.), I thought I would offer a knowledgeable perspective.
I have had long discussions with one of the primary people within the Fundacion PostgreSQL (Alvaro) and his heart is in the best interest of the community, even if Postgresql.org, PGEU and PGCAC do not agree. You can see this demonstrated within Fundacion’s trademark policy. That said, Fundacion PostgreSQL did go about their actions in an incorrect way. There should have been an open discussion and they should have provided PGCAC the opportunity to resolve the trademark issues on their own. It is also true that while I believe PGEU and PGCAC believe they are protecting the community, if they were interested in positive community growth and collaboration, they would not be taking the approach they currently are. The current path has far reaching implications that PGEU and PGCAC do not see.
Further, the PostgreSQL Community Association of Canada and Fundacion PostgreSQL have resorted to terrible language in representing what is actually going on within the disagreement. Using language such as, “An attack on our community” or “PostgreSQL attacks the community” is immature at best and at worst an intentional decision to use good faith and mindshare against what is largely just a disagreement that could be solved with an active mediator and a few phone calls. If this disagreement is about the best interest of the PostgreSQL community, shouldn’t that involve discourse, honesty, transparency, and kind communication?
(1) Internet consulting.
(2) Internet presence provider- DNS hosting.
(3) Commercial internet support for database applications development and implementation including the ability to host internet domains (as an internet service provider) and provide a wide range of web site development, programming and information technology services, namely computer software architecture, design and/or development services.
(4) Computer hardware sales and service.
The solution to the whole problem is simple; a single contract that states:
The contract should not contain language in regards to future potential filings that involve but are not exclusive to the word Postgres or PostgreSQL. There are already a number of filings worldwide that use Postgres or PostgreSQL as part of an overall mark inclusively such as Postgres Pro, Postgres Plus, Postgres Always On and Postgres Enterprise Manager, all of which are not owned but PGCAC or PGEU.
Because it is the right thing to do. Otherwise this whole affair is going to end up costing one entity or another way too much money for no purpose. There is no clear distinction on who would legally win, and in either situation the main sufferers are the PostgreSQL community. Let’s have the parties show an act of kindness for the betterment of everyone involved.

With 2020 firmly in the rear view mirror, it is time to look forward and down the highway of 2021. The organizers of People, Postgres, Data have gathered over chat, email, phone, and even a few socially distant, in-person events to determine a strategy for continuing as the most influential and positive community for all things Postgres related.
Sad face
The goal is to resume in-person events. However, out of concern for the health and comfort of our global community, we have made the decision not to host any in-person events until Q4 of 2021. We are prepared to wait until 2022 if that is what the health officials recommend. We know that many will find this news disappointing and we are working diligently to ensure that the health and education of our community is the top priority.
Happy face
We are continuing our popular webinar series, adding new presenters with pertinent content for all of our attendees. We will be adding more professional development and data problem solving topics to our library, and we will no longer be limiting education to just Postgres, as many data and human problems are neutral in the particular platform we happen to enjoy. If there’s a topic you’d like to present or see, we’d love to hear from you!
Ecstasy
Postgres Conference 2021: Digital will be happening in May of this year! An overwhelming feeling of great happiness and excitement has our dopamine pumping, and the whole People, Postgres, Data team is basking in it.
As an all digital conference, we will offer a similar environment to what our community has come to expect: best in class content, professionalism, and top-tier educational opportunities for all who attend! Keep your eyes peeled over the next few weeks for more information on speaking opportunities and how to attend!
Henrietta Dombrovskaya, Diversity, Equity, and Inclusion member for PostgresConf as well as Chicago Postgresql organizer nominated for Technologist of the Year!
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.
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.
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.
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
Scale, already built
We had a call with an ecosystem partner recently about a user that has over 20TB residing in our most beloved database. The response from the partner? “They are going to fall over.” It was an interesting response and also shows a lack of understanding of the absolute power and flexibility of Postgres implementations. This production installation (in the manufacturing industry) does not fall over and it sails over the waves like the 20’ swells don’t exist. The World’s Database is already scale built!
CFP Closes June 3rd! Submit your presentation now!
Early bird tickets now available! Get your tickets today as we expect this year to sell out!
The International Postgres Conference Series known as PostgresConf has the mission of “People, Postgres, Data.” It is based on the belief that taking care of and providing opportunities for people is our core goal.
In the coming months Co-Chair Amanda Nystrom will be spearheading a professional development series focused on the People part of the “People, Postgres, Data” mission. It will include articles, workshops, and, if all works out, a track at the event in 2020 at Times Square, New York City. We are excited to be expanding our serving of People through this opportunity.
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 areas including dates, venues, or a desire to join the amazing People, Postgres, Data team, let us know at organizers@postgresconf.org.
Join our community
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.