Joshua D. Drake Blog Posts

PGConf US in partnership with SeaPug is pleased to announce that the call for papers for PostgreSQL Conference US Local: Seattle is now open. 

National Diamond Sponsor

The call for papers will be open from May 16, 2017 until July 2, 2017. Speakers will be notified of acceptance/decline no later than July 8.

The two track, two day conference is a perfect opportunity for the Vancouver, B.C., west coast, and Rocky Mountain regions to join the PostgreSQL community and increase their knowledge.

National Platinum Sponsor

Breakdown of the Conference Layout: 

• August 11th: Training
• August 12th: Breakout Sessions 

All selected presenters will receive free entry to the breakout sessions (trainings are extra). There are no grants for travel and accommodations. We encourage everyone to submit a talk or training to one of our very first PostgreSQL Conference US Local events and be a part of growing the PostgreSQL community.

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!

Join us for a special presentation with PostgreSQL experts who will be in town for DataLayer 2017.

Food and refreshments will be provided, so please be sure to RSVP.

Thank you to OpenSCG for sponsoring our food and soft drinks, and fibercove for hosting us! Beer sponsor TBA.

• The event starts at: 6 pm 
• Networking and food/drink : 6:15 pm 
• Announcements and updates: 6:30 pm   

Presentations:
• "Softlayer vs RDS/AWS: A price to performance perspective" - Joshua D. Drake, Command Prompt, Inc.

• "PostgreSQL on Debian and apt.postgresql.org" - Dr. Michael Meskes, CEO of credativ (http://www.credativ.com/)

• "Top 10 Mistakes When Migrating From Oracle to PostgreSQL" -- Jim Mlodgenski, CTO of OpenSCG
 
About our Speakers: 

Joshua D. Drake of Command Prompt, Inc. (https://www.commandprompt.com/), is a PostgreSQL Consultant who has consulted on PostgreSQL since Postgres95. Throughout his PostgreSQL career he has performed a variety of functions within the community including releasing an O'Reilly book on PostgreSQL, as well as being part of the sysadmins and advocacy teams He ran a biannual conference series dedicated to PostgreSQL from 2007 - 2011. He is a former Director for SPI (the non-profit for PostgreSQL.org). Drake is also a Founder of United States PostgreSQL, as well as a co-organizer and Chair of PGConf US.

Dr. Michael Meskes is President and CEO of the credativ Group, an industry leader in free software services with offices in five countries. Its Open Source Support Centers employ leading members of a number of Open-Source projects. He has been Open-Source developer for twenty years working on different Open-Source projects among which Debian and PostgreSQL are most widely known. He also has done a lot of Open-Source related presentations on all sorts of events doing a lot of Open-Source evangelism.

Jim Mlodgenski is CTO of OpenSCG, a leading enterprise open source services company, with a central focus on PostgreSQL. He has been part of the PostgreSQL community for over a decade, as an architect and sales engineer. He is a Director for the U.S. PostgreSQL Association, as well as an organizer of the Philly PostgreSQL User Group and a Co-organizer of the NYC PostgreSQL User Group. He Is also a co-organizer of PGConf US, the largest PostgreSQL conference in the U.S.

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.

Why did you attend PgConf US?

Our company is exploring the use of PostgreSQL as an additional DBMS choice to support Vertex Enterprise, our tax technology platform. Attending the conference offered me an opportunity to immerse myself into a variety of topics around PostgreSQL, as well as the chance to interact with other users to tap into their experiences.


Tell us a little bit about your project or how you use PostgreSQL:

Vertex Enterprise is a global tax management end-to-end solution that integrates all tax processes with Enterprise Resource Planning (ERP) and business intelligence (BI) systems on a single platform using a tax performance engine.   The solution is a blend of technologies that surround a Java based processing and calculation engine. This includes rich UI's, import, export, business intelligence / reporting, and big data integration. The foundation of our database leverages a multi-dimensional database structure, as well as other structures whose design varies based upon the needs of a particular function so that we can optimize performance. (ie. import/export/reporting).

The official brochure provides a high level overview of the capabilities and interfaces that our DBMS must support.  

Why did you chose PostgreSQL for your project?

PostgreSQL checks many of the boxes that we are looking for in our consideration of an additional DBMS option.


Some of these include:

* Performance
* Lower cost
* Multi-tenancy support 
* Suitable for deployment on premise, in a hosted environment, and in the cloud
* Industry acceptance
* Ease of administration on locally administered instances
* Features characteristic of an enterprise strength database (auditing, partitioning, replication, procedural language support)


This was your first PGConf US, was it a last minute decision? Do you think it was worth it? If so, why?

The conference was on our radar since the beginning of the year, and it exceeded expectations. Listening to and interacting with actual contributors to the product is not something you have the opportunity to do at many conferences. The sessions covered a variety of topics around PostgreSQL that were of interest (performance, tuning, feature discussion, lessons learned, cloud deployment options, optimization, etc).


Would you attend PgConf US again?

Yes, definitely. 


Are you interested in contributing to the community and if so, in what fashion?

My "day job" keeps me pretty busy, but as far as sharing our experience with PostgreSQL, I am willing to contribute in that way :) .

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.

The following table contains a summary profit and loss statement for PostgresConf US 2018.

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

• Building Your Data Warehouse On Top Of PostgreSQL - Episode 186
• More than a Refresh: Stephanie Kirmer, Data Scientist for Saturn Cloud

1. https://www.socialworktoday.com/archive/072417p32.shtml