Joshua D. Drake Blog Posts

An act of kindness for the PostgreSQL community

Since at least 2021 there has been a disagreement between Postgres related non-profit organizations. On one side are two affiliate non-profits for Postgresql.org; on the other is a relatively unknown non-profit out of Spain. Lines have been drawn, feet have dug in, and a lot of unproductive discourse has occurred. This has culminated in legal action, bad blood, and some poor decisions. 

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?

Some facts:


  1. The first appearance of a PostgreSQL trademark outside of Canada wasn’t until 2018.
  2. The trademark PostgreSQL in the European Union was not registered until 2018.
  3. The trademark in Canada was registered in 2003 (filed in 1999).
  4. The trademark in Canada does not accurately represent PostgreSQL as the services it was registered under are:

(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

The solution to the whole problem is simple; a single contract that states:

  1. That the term PostgreSQL is trademarked by the PostgreSQL Community Association of Canada
  2. That the Fundacion PostgreSQL relinquishes all property and rights to the mark PostgreSQL held in Spain and assigns them to the PostgreSQL Community Association of Canada
  3. The PostgreSQL Community Association of Canada forgoes any punitive damages or secondary costs
  4. That the Fundacion PostgreSQL forgoes any punitive damages or secondary costs

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.

Why forgo punitive damages or secondary costs

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.



Joshua D. Drake     September 05, 2023

Pivotal Greenplum and PostgresConf!

Pivotal Sponsor Highlight Blog for PostgresConf 2019

 

Written by:

Jacque Istok, Head of Data, Pivotal

 

1. Greenplum has its own community; what do you hope to achieve by joining the Postgres community and PostgresConf?

Both interest and adoption of Postgres have skyrocketed over the last two years, and we feel fortunate to be a part of the extended community. We have worked very hard to uplevel the base version of Postgres within Greenplum to more current levels and to be active in the Postgres community. We see Greenplum as a parallel (and analytic focused) implementation of Postgres, and we encourage the community to continue to embrace both the technology and the goal of the Greenplum project, which is Postgres at scale.

 

2. Are you planning to provide any new tech (PG features, etc.)?

This year we plan to announce several new things for both Greenplum and Postgres. We’re introducing new innovations in our cloud offerings in the marketplaces of AWS, Azure, and GCP. We also have major news about both our natural language at-scale analytics solution based on Apache Solr, and our multi-purpose machine learning and graph analytics library Apache MADlib. The next major release of Greenplum is a major focus as well, differentiating Greenplum from each of its competitors and bringing us ever closer to the latest versions of Postgres.

 

3. Are there any rising stars in the community you’d like to give props to?

While it seems a little self-serving, I would like to take the opportunity to give props to the Pivotal Data Team. This team is a 300+ worldwide organization that helps our customers, our prospects, and the community to solve real world and really hard data problems—solved in part through Postgres technology. They all attack these use cases with passion and truly make a difference in the lives of the people that their solutions touch. I couldn’t wish to work with a finer group.

 

4. What is the number one benefit you see within Postgres that everyone should be aware of?

The number one benefit of Postgres is really its flexibility. This database chameleon can be used for SQL, NoSQL, Big Data, Microservices, time series data, and much more. In fact, our latest analytic solution, MADLib Flow, leverages Postgres as an operational engine. For example, Machine Learning models created in Greenplum can be pushed into a restful API as part of an agile continuous integration/continuous delivery pipeline easily and efficiently—making Postgres the power behind what I still like to think of as #DataOps.

 

5. What is the best thing about working with the Postgres community?

 

I deeply admire the passion and consistency of the community behind Postgres, constantly and incrementally improving this product over decades. And because Greenplum is based on Postgres, we get to interact with this vast community of talent. We are also able to more seamlessly interact with ecosystem products that already work with Postgres, making the adoption of Greenplum that much easier.

 

6. Tell us why you believe people should attend PostgresConf 2019 in March.

 

PostgresConf is going to be awesome, and I can’t wait for it to start! With Pivotal, Amazon, and EnterpriseDB headlining as Diamond sponsors, Greenplum Summit (along with multiple other summits), and high-quality speakers and content across the board, this year’s PostgresConf promises to be bigger and better than ever and surely won’t disappoint.

 

We’re thrilled to be back to present the second annual Greenplum Summit on March 19th at PostgresConf. Our theme this year is “Scale Matters”, and what we’ve seen with our customers is that every year it matters more and more. Our users are part of organizations that are generating tons of data and their need to easily and quickly ingest and interrogate all of it is paramount. This is true even more now than ever before as the insights that can be found not only help differentiate them from their competitors, but are also used to build better products and increase customer loyalty.

 

The day will be filled with real-world case studies from Greenplum users including Morgan Stanley, the European Space Astronomy Centre, Insurance Australia Group, Purdue University, Baker Hughes (a GE company), Conversant, and others, plus presentations and deep-dive tech sessions for novices and experts alike.

Joshua D. Drake     February 14, 2019

People, Postgres, Data


People, Postgres, Data is not just an advocacy term. It is the mission of PostgresConf.Org. It is our rule of thumb, our mantra, and our purpose. When we determine which presentations to approve, which workshops to support, which individuals to receive scholarships, which events to organize, and any task big or small, it must follow: People, Postgres, Data. It is our belief that this mantra allows us to maintain our growth and continue to advocate for the Postgres community and ecosystem in a positive and productive way.

When you attend PostgresConf the first thing you will notice is the diversity of the supported ecosystem; whether you want to discuss the finer points of contribution with the major PostgreSQL.Org sponsors such as 2ndQuadrant or EnterpriseDB, or you want to embrace the Postgres ecosystem with the Greenplum Summit or TimeScaleDB.

The following is a small sampling of content that will be presented April 16 - 20 at the Westin Jersey City Newport:

Learn to Administer Postgres with this comprehensive training opportunity:

Understand the risks of securing your data during this Regulated Industry Summit presentation:

Struggle with time management? We have professional development training such as:

Educate yourself on how to contribute back to the PostgreSQL community:

We are a community driven and volunteer organized ecosystem conference. We want to help the community become stronger, increase education about Postgres, and offer career opportunities and knowledge about the entire ecosystem. Please join us in April!

Joshua D. Drake     February 27, 2018

It's done, the PostgreSQL community rocks.

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.

Joshua D. Drake     April 04, 2017

Postgresql and The great development modernization debate

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.

Joshua D. Drake     May 13, 2019

3 presentations, 1 PGConf: NYC Mini!

We are having yet another PGConf Mini in NYC. The event is scheduled for December 14th, 2017 and Work Bench is hosting:

 
 
The event is part of the PGConf Mini series and is free to attend. The PGConf Mini series works directly with user groups and external communities to organize events for the local community. The events are held as a larger meetup style event with networking opportunities and up to 4 presentations. The current agenda for the latest PGConf Mini: NYC is:
 
Agenda: 
 
• 6:30 - 7:00: Jonathan Katz, (TBD), Postgresql Contributor and PGConf Chair Emeritus

Efficiently and Safely Propagate Data Changes Without Triggers!

 

Prior to PostgreSQL 9.4, the primary way to distribute data-driven changes across multiple tables was to use triggers. While triggers guarantee that these changes will be propagated, they can have a significant impact application performance, both technically and with development time (see: "debugging"). PostgreSQL 9.4 introduced logical decoding, which provides a way to stream all changes in a database to a consumer. Using a logical decoder, you can read all changes that are made in a table into your programming language of choice to perform many tasks: cache invalidation, data propagation, submitting changes to remote services, and more. Many PostgreSQL drivers, such as psycopg2 and JDBC support the logical replication protocol, which lets you easily stream your database changes to be manipulated using your favorite programming language. This talk will demonstrate how you can setup logical decoding for your application, look at architecture strategies for working with a logical decoder, and look at a case-study that shows how using logical decoding led to a big performance boost over a similar trigger-based system.
 
• 7:00 - 7:30:  Kevin Jernigan, Senior Product Manager, Amazon
Technical Architecture of Postgres Aurora 
 
Amazon Aurora is a cloud-optimized relational database that combines the speed and availability of high-end commercial databases with the simplicity and cost-effectiveness of open source databases. The recently announced PostgreSQL-compatibility, together with the original MySQL compatibility, are perfect for new application development and for migrations from overpriced, restrictive commercial databases. In this session, we’ll do a deep dive into the new architectural model and distributed systems techniques behind Amazon Aurora, discuss best practices and configurations, look at migration options and share customer experience from the field. 
 
• 7:30 - 8:20: Joshua (JD) Drake POSTPONED due to flight cancellation)
The Power of Postgres Replication, Postgres Expert - Lead Consultant Command Prompt, Inc and Co-Chair PGConf!
 
With PostgreSQL v10 a new replication engine has come to town. Let's explore Postgres Logical Replication, how to use it, optimize it and let it best fit in with your organization. We will also discuss its interactions with external tools as well as Binary Replication and features such as Hot Standby. 
 
 
 
 
Joshua D. Drake     November 20, 2017

An Invisible Disease

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

24x7x365 Postgres & Linux servicesCommand Prompt, Inc.The last of the original Postgres companies

Sponsored

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








  1. https://www.socialworktoday.com/archive/072417p32.shtml
Joshua D. Drake     May 19, 2021     eds postgresql

PGConf Local: Seattle 2017 registration open and schedule published

The first ever PGConf US Local: Seattle event is happening in partnership with SEAPUG on August 11th and 12th at the Sheraton Downtown Seattle! On August 11th we have four training options available:
  1. Mastering PostgreSQL Administration by Bruce Momjian
  2. Migrating from Oracle to PostgreSQL by Jim Mlodgenski
  3. Postgres Performance and Maintenance by Joshua (JD) Drake
  4. Database Automation by Robert Bernier 

Tickets are now available!


On August 12th we have 14 break-out sessions between the Development and Operations tracks. A sample of our break-out sessions is available below but please check the full schedule for all of the fantastic content!
We would not be able to produce PGConf Local: Seattle 2017 without the generous support from our sponsors:
    Sponsorship opportunities for the conference are still available. If you use Postgres, support Postgres, or if you are looking to recruit a local Postgres expert, this is a great opportunity. Become a part of our dynamic and growing ecosystem! The prospectus is available at:
    Joshua D. Drake     July 11, 2017

    PostgresConf US 2018: A Review of the largest PostgresConf ever and a recap of the last 12 months!

    The PostgresConf team wanted to provide some information on the performance of PostgresConf US 2018 and events over the past year, as well as potentially answer some pending questions. Ultimately our goals are about people, which is why our motto is, "People, Postgres, Data." With each event we hold, each talk we accept, and how we train our volunteers, we make sure people (the benefit for and to), postgres, and data are considered and included. If there is no benefit or consideration to the growth of people, it is not an option.


    With that in mind, please read on to see how our focus on people, Postgres, and data had an impact on the community over the last year.

    Since PostgresConf US 2017 we have had events in:
    • Philadelphia 
    • Ohio (in combination with Ohio Linux Fest) 
    • South Africa 
    • Seattle 
    • Austin 
    • Jersey City (PostgresConf US 2018) 
    • Nepal 
    All of these events are non-profit and volunteer organized.





    PostgresConf US 2018


    Logistics


    • Days: 5, 2 for training, 3 for Breakout sessions and summits
    • Official Attendance #: 601
    • Content: Over 207 sessions submitted
    • Sessions: Over 108 sessions provided 


    Partner Support (Sponsors): 28


    We had a record level of support from partners this year and due to this support we are going to be forced to find a new venue for next year. Our Jersey city location no longer has the capacity to hold us. This will increase costs but initial indications are that our partners understand this and are willing to support us financially to help continue the success of our efforts and keep costs reasonable for attendees.


    Diversity


    This year we were able to work with Women Who Code NYC. They provided many volunteers and we provided them with the ability to experience some of the best Postgres based content available, at no charge. We expect great things from this budding relationship in the future.


    Professional Growth


    We held a Career and Talent Fair. A dozen companies were present to connect with potential employees.

    We also held a surprisingly well attended speed mentoring session for potential employees (Especially helpful for many of the WWC) on resumes and interview practices.

    Leadership


    This year saw the continued elevation of our primary leadership: Viral Shah, Lloyd Albin, Amanda Nystrom, and Debra Cerda. They continued to increase their presence and responsibility within the conference and dedicated hundreds of hours voluntarily to the growth of people. Our international members have also increased their leadership roles with our on-the-ground teams in South Africa and China.


    Summits



    We had our standard Regulated Industry Summit but also a Greenplum Summit. As I am sure you are aware Greenplum is an Open Source, Postgres based MPP database. They were by far the most popular booth in the entire conference and their summit was very well attended. The relationship with Pivotal and the success of the Greenplum Summit allowed us to learn new ways to bring together the entire Postgres Ecosystem. We expect to run a minimum of 3 more summits at PostgresConf US 2019.



    Contribution


    We were able to have several excellent (and long) meetings with leaders of Pivotal, Microsoft, Google, and Amazon on how they can begin contributing more back to Postgresql.org. All of them expressed a deep drive to contribute and a desire to learn more about the core community. Of particular note is Google, who would like to contribute the following back to the community:

    https://github.com/google/pg_page_verification

    We discussed with them the process and various changes they would need to make (license and code style, etc.). We also educated them on the PostgreSQL.Org rigorous review process.

    Microsoft is reviewing how they can contribute but they showed an interest in build farm nodes, professional technical writers to help with docs, and potentially code contribution to our Windows port.

    International Collaboration

    The Chinese Open Source Promotion Union launched the Chinese Postgres Association. We invited them to PostgresConf US and introduced them to the United States Community. We expect great things from the Chinese community in the future.

    Future


    As we continue to build up our on-the-ground teams, we will likely hold less events in the U.S. this year. We will instead be focused on a smaller number of events in the U.S. and adding events in China and Europe. We have had an amazing amount of support from the Chinese community and the current goal is 1000 attendees for that conference.

    Our current plan of events for the U.S. are


    • San Jose (October 2018) 
    • Philadelphia 
    • PostgresConf US (Manhattan) 

    Future International Events


    • October 2018. 
    • Spring of 2019. 
    • Spring of 2019. 

    This may change as we are actively recruiting on-the-ground teams to help us grow the community.

    Collaboration


    Our goal is collaboration and growth with other PostgreSQL community and Ecosystem efforts. We want to allow each potential community member to find a home. A place that they feel positive about contributing to the community as a whole. As we continue to grow as a community, it is vital to recognize that each member has their own needs, desires, and return on investment requirement (professional or personal) that they are seeking.

    Tidbits of note



    On DBEngines PostgreSQL is the 4th most popular database but the significance is that of the other 3, we are the only ones that are growing in popularity. 
    Joshua D. Drake     May 07, 2018

    From mountains to busy: Launching Digital events and latest news

     

    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.

    Events

    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!

    Meetups

    We have seen the launch of three new meetups this month:

    • Los Angeles Postgres The first meetup is planned for late October or early November as we continue to build the Silicon Beach community.
    • Toronto Postgres Similar to Los Angeles, the first meetup is planned for late October or early November.
    • Charm City Postgres This meetup was formed by long time community member Robert Treat.

     

    Several other meetups are growing quickly: 

     

    Interested in speaking or hosting a meetup? Contact us and we’ll connect you with the right people! 

    Learn

    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.

    Ecosystem

    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.org

    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.

    Joshua D. Drake     August 23, 2019