That's right, folks; the time has come. 

2ndQuadrant Sponsor Highlight Blog for PostgresConf 2019

 As part of the countdown to PostgresConf US 2019, learn more about about featured Platinum Sponsor 2ndQuadrant, including their commitment to partnering with and contributing to the Postgres community.

Tell us about the recent uptick in Oracle to Postgres migrations.

Licensing costs of Oracle is a significant factor for businesses looking to migrate towards PostgreSQL. Not only is PostgreSQL a more cost effective solution, but it provides enterprise-level capabilities and customization options. The increasing demand for migration services from Oracle to PostgreSQL can also be attributed to the availability of PostgreSQL in the cloud.

Where do you see the Postgres market going?

PostgreSQL has been gaining traction with every release; interest and usage by large enterprises worldwide is growing exponentially due to the robust capabilities it provides. 2ndQuadrant intends to continue their active contributions in development and supports the overall growth of PostgreSQL.

 Do you have any big wins this year?

2Q PGConf 2018 had a successful second year bringing together PostgreSQL developers and users. Both speakers and attendees enjoyed the combination of technical and use case topics as well as the diverse range of networking opportunities. 

Sri Rangarajan, Lead Software Engineer at Enova International, commented saying he appreciates 2ndQuadrant’s hard work in “promoting and fostering a savvy, healthy and helpful community to welcome newcomers just like [it] did for [him] 5 years ago!”

For the second year in a row, PostgreSQL has been named DBMS of the Year by DB-Engines. This shows that developers and users alike are acknowledging the robust and versatile capabilities that it has to offer.

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

PostgreSQL's advanced features cater to a broad range of use cases all within the same DBMS. Rather than going for edge case solutions, developers are relying on the absolute reliability of the hyperconverged database to simplify their production deployments.

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

The Postgres community is one of the easiest global communities to work with. There is an open mindset all around and a common goal of growing the Postgres ecosystem as a whole. 

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

Conferences are a great way for people in the PostgreSQL community to come together and share knowledge and ideas, which is the true spirit of open source. It is very exciting to see into the future developments of the project from the people who contribute so much to its growth.

It is a great way for members of the community to come together in person to share knowledge in different areas of the technology, describe practical use cases, and give sneak previews into cutting edge technologies for future versions of PostgreSQL.

About 2ndQuadrant:

2ndQuadrant provides PostgreSQL Solutions for the Enterprise - reliably deploying them on the platform of your choice and providing 24/7 Production Support. Our solutions address all aspects of your database ecosystem, ensuring high availability, disaster recovery, backup & failover management, and much more. 

Moreover, we provide tools to make your deployment process simple and reliable. With over 100 years of combined code contributions to the PostgreSQL project, our engineers ensure that your PostgreSQL solutions are fully supported in your production environment.

Visit the 2ndQuadrant team in the Exhibit Hall in the Metropolitan Ballroom on Wednesday, March 20, and Thursday, March 21.  

Check out the full schedule for PostgresConf US 2019, and buy your tickets soon!

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

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.

As part of the countdown to PostgresConf US 2018, learn more about the engaging content and our Diamond and Platinum sponsors for this year in our Sponsor Spotlight Series.

Jacque Istok, is the Head of Data for Pivotal, one of our Diamond Sponsors for PostgresConf US 2018. Pivotal is hosting the first annual Greenplum Summit at PostgresConf US 2018, with lots of great Greenplum and Postgres-related content. Read what Jacque has to say bout Greenplum and Postgres, as well as why to attend the Greenplum Summit: 

Greenplum is an Open Source variant of Postgres; what benefits do you bring to the table over vanilla Postgres?

Postgres is a powerful ORDBMS, but as your data scales, the only way to keep up is to buy bigger and bigger machines to run on. It suffers from the same problems that all SMP databases do: you can only get as big as the machine you’re running on.

With Greenplum you can put a subset of your data on a Postgres database on one reasonably-sized machine, and another subset on a second machine, and so on. All of your users and applications can then query one of these Postgres databases as if all the data was in a single location - making your data scale limitless. Greenplum manages the distribution, data shuffling, and querying of all of your data across a magically sharded implementation of Postgres databases.

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

The Postgres community represents some of the most passionate and knowledgeable creators, developers, and users of database technology of our time. We believe that the combination of Postgres and Greenplum becomes the software equivalent of what Oracle Exadata purported to be: an all-purpose database that can do both transactional and analytical workloads across multi-structured data. Simply put, the Greenplum community is looking to join with the Postgres community to further the understanding and adoption of these technologies.

Do you have plans for cross pollination of technologies with the two open source projects?

Greenplum forked from Postgres over 10 years, circa Postgres 8.2. Greenplum 5.0 is based off of Postgres 8.3, with our next major release slated for Postgres 9.4 (current open source Greenplum is compatible with 9.0 as of this writing).

Likewise, we have Postgres committers working at Pivotal looking for opportunities to improve the Postgres code specifically for analytics. We are also ensuring that other projects related to Greenplum, like Apache MADLib, continue to be compatible with Postgres.

What challenges do you see working with the Postgres community as an open source fork?

The Postgres community is a long-running and very passionate group, and we want to be both collaborative and respectful in how we continue to grow our participation. We see the products as having synergies which complement each other very well, with some use cases that best fit Postgres, and others that best fit Greenplum. The use of either benefits the other as they both further adoption.

What would you tell a user who has a choice between Postgres and Greenplum about when they should use which system?

Postgres is a great ORDBMS that will scale to the performance of a single server. For analytical needs, being restricted to a small number of terabytes does not allow for the type of exploration that most organizations need. Because Greenplum is a Postgres compatible database, you can start out using Postgres and either convert to Greenplum underneath or leverage Greenplum alongside your Postgres systems (making data ETL a ton easier). This then makes the choice of which product to use for your particular use case clearer and clearer.

What is the number one barrier you see to contributing to the Postgres community?

The number one barrier we will have to contributing is not seeing the corresponding adoption of our technologies. We feel very strongly that both the transparency and removal of vendor lock-in make our open source commitment the only choice for users. I’m here to implore the community to embrace our technology with zeal and help us continue to drive more and more Postgres adoption in the world.

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

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.

Tell us why you believe people should attend PostgresConf 2018 in April.

PostgresConf is going to be awesome - with both Pivotal and Amazon headlining as Diamond sponsors - as well as the quality of speakers and their content. I wouldn’t miss it for anything.

We’re thrilled to organize the first annual Greenplum Summit at PostgresConf. Greenplum co-founder, Scott Yara, will give a keynote on April 18th relating to how data tells the story at the organizations that we help enable (#DataTellsTheStory), and his journey from SMP to MPP. Greenplum Summit on April 19th will be a full day packed with with great use case sessions and tech talks for novices and experts alike.

Check out the full schedule for PostgresConf US 2018, and buy your tickets soon!

The Chairs (myself, Jim Mlodgenski, and Amanda Nystrom) have recently decided to bring some visibility to charities that are close to our hearts. They are listed below:

• Joshua Drake: Navajo Water Project. The Navajo nation is approximately the size of West Virginia and has a population of over 150,000 people (300k in the tribe). Anywhere from 15% - 40% of the residents do not have access to running water. The Navajo Water Project aims to bring clean water to each person and family through support from those that donate. 
• Jim Mlodgenski: St. Jude Children’s Research Hospital. The hospital is one of the premier research hospitals for cancer and other life threatening illnesses for some of our most vulnerable people. Approximately one in 285 children in the U.S. will be diagnosed with cancer before their 20th birthday. Through donations, St. Jude’s provides treatment to those with cancer, and is actively dedicating resources to the research and cure for cancer. 
• Amanda Nystrom: ASPCA. The American Society for the Prevention of Cruelty to Animals (ASPCS) was the first humane society to be established in North America, with the goal of providing kind and respectful treatment to animals under the law. Unlike humans, cases of animal abuse aren’t compiled but studies have shown a correlation between domestic violence and animal abuse. The ASPCA prevents animal homelessness and actively rescues animals from dangerous and/or cruel situations.

Upcoming Webinars

With the Coronavirus causing the conference market to dry up for 2020, we at Postgres Conference have pivoted to ensure that we continue to provide quality Postgres content to the world of People, Postgres, Data. We have been performing multiple webinars per month. Here is the current schedule and you can register (free) here:

• May 21, 11am PT: A Deep Dive into PostgreSQL Indexing
• June 2, 10AM PT: How to Move Data from Oracle to Postgres in Near-Real Time
• June 9, 11am PT: Community vs. Enterprise Open Source – Which is Right for Your Business?
• June 10, 11am PT: Bring Compression to Postgres at Zero Cost of Performance
• June 16, 11AM PT: Mostly mistaken and ignored PostgreSQL parameters while optimizing a PostgreSQL database
• June 30, 11am PT: Deeper Understanding of PostgreSQL Execution Plan: At plan time and run time
• July 15, 10AM PT: Working with JSON Data in PostgreSQL vs. MongoDB
• June 17, 11am PT: Postgres vs. MongoDB for real-time machine learning on wind turbine data

Articles from the community

• Why work for hire could be limiting your company and yourself
• Build PostgreSQL extensions on Windows
• Operationalizing your PostgreSQL database health checks using SQL Notebooks
• Building fast refresh capability in Amazon RDS for PostgreSQL
• Multi-tenant data isolation with PostgreSQL Row Level Security

Coronavirus Resources:

• Open-Access Data and Computational Resources to Address COVID-19

• Friday, September 29, 2017: Trainings

Mastering Postgres Administration: Bruce Momjian

Postgres Performance and Maintenance: Joshua D. Drake 

• Saturday, September 30, 2017: Breakout Sessions (To be announced)