Joshua D. Drake Blog Posts

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

Digital Events

  • YugabyteDB Distributed SQL Webinars
    • A series of free webinars discussing technical opportunities with Distributed SQL. YugabyteDB is an Open Source, Postgres compatible Distributed SQL database.

News

Learn

 

Partner 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%. 

 

Joshua D. Drake     September 04, 2019

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 SeaPug is pleased to announce that the call for papers for PostgreSQL Conference US Local: Seattle is now open. 


PostgreSQL Conference US Local: Seattle is taking place August 11th and 12th 2017! Call for Papers is now open and presentations can be submitted here.



Image result for aws
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.
Image result for openscg
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.
Joshua D. Drake     May 16, 2017

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

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

Tuesday, May 16, 2017 6:00 PM to 9:00 PM @ fibercove
1700 S Lamar Blvd, Suite 338, Austin, TX

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.
Joshua D. Drake     May 11, 2017

Why did you attend PgConf US?

We have been looking for high quality, experienced, professional support for our application’s database for some time. We have found it difficult to find help online… seemingly every phone number we called was just an answering service. When we heard that the companies offering the level of service we were looking for were all available in the same place, we couldn’t resist.

Tell us a little bit (one or two paragraphs) about your project:

Our project (VX and VO collectively named Victor) is a SaaS solution for 911 emergency response systems. Victor provides analytics and quality assurance tools and services, enabling agencies to assess performance, measure resource & deployment activity, model demand, optimize workload, and even generate financial estimates. For more information see our website.

Why did you chose PostgreSQL for your project?

Victor requires both time and spacial awareness, along with all the other things that are expected from an RDBMS. PostgreSQL is stable, secure, mature, well documented, open source, actively developed, community supported, and generally bad ass. The choice was easy.

As I understand it, attending PgConf US was a last minute decision. Do you think it was worth it? If so, why?

Absolutely! Our objective was to meet with vendors who were able to provide high quality support and we were successful. Additionally, we met a ton of super geniuses (Paragon, TimescaleDB, I’m talking about you) and learned more then expected. For example, we had no idea we could put raster images in PostgreSQL and process them with PostGIS… amazing!

Would you attend PgConf US again?

Yes… see above. Unrelated, but unbelievably cool, we met a guy named Solar… a PhD (from MIT!) passionate about carbon nanotubes.

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

Yes! …and here is our biggest piece of feedback.

It would be great if there was a clear point of entry for people like us… we have been using PostgreSQL for several years, have been through several upgrade cycles (we started on 9.0) and have no idea how our skills could be of use. We make SaaS applications, but make nothing in C. What else does the community need? How can we help?
Joshua D. Drake     April 19, 2017



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 :) .
Joshua D. Drake     April 10, 2017

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!

RSVP for upcoming scheduled events

  • January 26, 1pm ET: All we need to work with SQL is SQL
  • January 27, 1pm ET: PostgreSQL Forks and Knives
  • February 3, 2pm ET: Postgres for SQL Server Users
  • February 4, 1pm ET: Configuring PostgreSQL for Faster Analytic Query Performance
  • February 23, 1pm ET: Blockchain as a Database

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!

Joshua D. Drake     January 20, 2021