Community,
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.
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.
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
 |
| Mastering Postgres Administration: Bruce Momjian |
People, Postgres, Data,
Due to the health risks and travel restrictions created by the Coronavirus we unfortunately have to cancel Postgres Conference 2020 which was to be held at the Marriott Marquis on March 23rd, 2020 thru March 27th, 2020.
We want to thank all of our attendees, partners and volunteers for all the hard work we all put in to try and pull this event off. Sadly, the stars were not aligned this year. We now focus our efforts on Postgres Conference Silicon Valley 2020 and our Digital Events.
Thank you all for your patience and support,
Postgres Conference Chairs
It is late August, 2019. This is the time where we are usually prepping for the very busy fall season and not much else. However, this is the Year of Postgres and everyone is driving 200MPH down the ecosystem highway (321.8688/KPH). We are going to kick off this newsletter with some exciting information about the community.
PostgresConf has launched Digital Events! The goal of Digital Events is to open our education platform year round to all members of the community. Our first series of events will be held with our ecosystem partner YugabyteDB and their “Distributed SQL Webinar Series.” This is a series of free-to-attend Webinars exploring Distributed SQL from leaders in the field.
PostgreConf Silicon Valley tickets are going at a brisk pace and half day trainings are almost sold out. Register today to reserve your seat before prices go up on September 1st!
Right after Silicon Valley, PostgresConf South Africa is kicking off. This conference has grown by leaps and bounds over the last two years. We highly recommend attending for anyone who can!
PGConf.IN (India) has announced that their conference will be held in February 2020!
We have seen the launch of three new meetups this month:
Several other meetups are growing quickly:
Interested in speaking or hosting a meetup? Contact us and we’ll connect you with the right people!
Here is a short, great introduction tutorial on running PostgreSQL in Docker by Igal Sapir, Los Angeles Postgres organizer. Everybody has 13 minutes.
Shawn Wang from our friends at High Go has provided an insightful write-up on AES Performance.
TimescaleDB is running a “State of Postgres” survey. Please take five minutes and help them out! They have also announced a new Distributed Timeseries product.
VMWare has just acquired Greenplum and PostgreSQL supporting company Pivotal.
PostgreSQL versions 11.5, 10.10, 9.6.15, 9.5.19, 9.4.24, and 12 Beta 3 are now out in the wild and addressing several important security concerns and bug fixes.
---
Have news you’d like included in future newsletters? Contact us.
As Postgres Conference pushes forward in the brave new world, we evolve and increase the ability for the People, Postgres, Data community to succeed. As a part of our positive adaptation we have a new website that features upcoming events, professional content (written and video), and the best in our written community via “Community Content”.
In an effort to provide a modern, friendly, and inclusive community platform, we have launched a Discord server for all things Postgres. We are providing a helpful experience with rule #1 being: Be Nice. Our discussions will branch out beyond the core of PostgreSQL and provide a forum for success with Postgres and related technologies. Join us for what is guaranteed to be a refreshing experience for the community: https://discord.gg/tjxNBCz
We are seeking feedback from our community on 2021 in-person events. We are currently considering the East Coast event for October 2021 and the West Coast event for December 2021. Please help us in determining the type of event you would like to participate in!
We currently have the following webinars scheduled through October:
