Joshua D. Drake Blog Posts

People and Postgres: April 17th, 2019

Welcome to the first of what we hope will be a thriving and productive way to interact with the People, Postgres, Data community!

The goal of this newsletter is to let our community know the ins-and-outs of what is happening in the world of Postgres and the Postgres ecosystem. Let's start from the top: 

  • Ecosystem news

    • JD, Co-Chair of PostgresConf, was recently part of the Inside Analysis podcast: The Evolving Enterprise. This podcast is not only available on the Internet but was live on 20 radio markets. 
    • Crunchy Data Collaborates With Center for Internet Security® To Continue Advancing PostgreSQL Security For Enterprise
    • The Distributed SQL Summit is being held at PostgresConf Silicon Valley on September 20th, 2019.
      • This unique "event within an event" strategy was spearheaded by PostgresConf with the Regulated Industry summit years ago and it continues to grow with events such as the AWS Migration Day and the Pivotal Greenplum Summit. The Distributed SQL Summit is a vendor neutral single day event specializing in providing high quality Developer, Architect and other Practitioner content on deploying and developing production quality products and services over Distributed SQL. It is sponsored by:
Joshua D. Drake     April 17, 2019

Join the fantastic and growing Postgres community in Cape Town, South Africa for a single day event on October 3rd, 2017! The event is being hosted by fellow Postgres advocates who travel from South Africa each year to attend our National Event in order to increase their knowledge of Postgres and be a part of the community. This year they are joining us and making a commitment to build out our International community and conferences!

This single day event takes place at the same venue as PyCon South Africa and is scheduled the day before PyCon to ensure the greatest possible value in attending.

Image result for PGConf US

Local events are designed to bring comprehensive educational content and networking opportunities to the "local" Postgres community where the event is being held. They are perfect opportunities to show support for Postgres, find leads, and build relationships with other professionals and companies using and supporting Postgres.

Joshua D. Drake     August 15, 2017

We are pleased to announce that Early Bird tickets to Postgres Conference 2019 are now available. Whether you are seeking a world class big data and analytics learning opportunity from the Greenplum Summit, a deep dive from the Google Cloud Summit, Regulated Industry Information from the Regulated Industry track, or a dizzying amount of learning opportunities from over 100 breakout sessions, PostgresConf 2019 is the show not to miss! Oh, and did we mention there will be training options as well?

Register here:

https://postgresconf.org/conferences/2019

Call For Papers is still open! Submit your presentation at the above link.
 
 Postgres Conference 2019

PostgresConf would be impossible without the generous support of our sponsors including:
EnterpriseDB, Pivotal, Google, Microsoft and 2ndQuadrant.

Thanks for all of the support and we look forward to seeing you in March!

The Postgres Conference Organizer Team

Joshua D. Drake     December 11, 2018



Seattle Postgres and People, Postgres, Data were present at the 20th Anniversary Event of LinuxFest Northwest this weekend! The “Fest” is a conference built around Free and Open Source Software, taking place in Bellingham, Washington. It is a true gathering of over 2000 Open Source practitioners. There was also a well attended Postgres Track and an “Ask the experts” panel.

Highlighted Find

Also at LinuxFest Northwest was YottaDB. YottaDB uses the PostgreSQL wire protocol to allow universal driver access to their in-memory transactional database. This has become a popular way to utilize the maturity of the PostgreSQL code base and reduce overhead in having to maintain a protocol and drivers.

Ecosystem Content

Requesting Feedback

We are looking for good dates to host PostgresConf Philly in July/August 2019 and we are actively reviewing new markets for other Postgres Conference events including Texas, Vancouver B.C., and Seattle. If you have feedback on opportunities in these areaa including dates, venues, or a desire to join the amazing People, Postgres, Data team, let us know at organizers@postgresconf.org.

 

Noteworthy Commits & Releases

The PostgreSQL git repo was largely bug fixes and updates the past couple of weeks but we have some great releases including migration tools and Distributed SQL:

 

Join our community

Upcoming Events



People, Postgres, Data and The World’s Database

 

The World’s Database celebrates all of Postgres, including whichever version, fork, or hybrid used to build yourself, your business, or your hobby. We have Open and Closed Source technologies. We have amazing extensions (TimescaleDB), unique implementations (Yugabyte), and respected forks to solve specific problems such as Greenplum, Azure, and Aurora. We have meetups where professionals can gather to collaborate and network in all major U.S. markets. Most importantly we are an inclusive community celebrating everything surrounding the maturity, extensibility, and growth of the Postgres ecosystem.

Joshua D. Drake     April 29, 2019

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

We are pleased to announce that PostgresConf 2019 will be held at the Sheraton Times Square March 18th - 22nd, 2019. 
 
 
Following on the success of PostgresConf 2018, 2019 will include five days with added training and partner summits.
 


March 18th and 19th will have immersive training. Instructors are encouraged to submit half and full day material for consideration. The preferred topics are centered around Postgres but anything People, Postgres, or Data related will be considered.

Monday, March 18th through Friday, March 22nd will host several partner summits, including popular and upcoming topics within the Postgres community and the annually hosted Regulated Industry Summit. Break out sessions will be held from Wednesday - Friday.

In addition to the partner summits, PostgresConf 2019 will offer multiple program tracks with Postgres related topics including (but not limited to): 

  • Postgres Internals
  • Postgres Administration
  • Operations and Development
  • Data
  • Cloud
  • Database Security and Compliance
  • Use Cases
  • Regulated Industries
    • Telecommunications
    • Healthcare and life sciences
    • Railroad, airline and pipeline transportation
    • Oil and gas
    • Electric power and transmission
    • Financial services and trading 
Important Dates:
  • Call for Papers Open: 09/12/2018 
  • Call for Papers Close: 01/11/2019 
  • Confirmation/Acceptance: 01/18/2019
Can't wait until March? Join us at our West Coast event, PostgresConf Silicon Valley, October 15th and 16th, 2018 at the Hilton San Jose.
 
About PostgresConf:


PostgresConf is a global nonprofit conference series with a focus on growing community through increased awareness and education of Postgres and related technologies. PostgresConf is known for its highly attended national conference with the mission of:

 
 
Joshua D. Drake     September 25, 2018

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

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

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

Andreas Scherbaum recently tweeted, “Speakers: it is NOT OK to even consider drinking alcohol during a talk! No matter how complicated your talk topic is.” The tweet has caused an interesting debate on Twitter and Facebook. It also caused me to run a poll via @amplifypostgres on the matter.

At the time of this writing almost 70% of the votes on the poll either don’t care or don’t think it is unprofessional for a presenter to drink alcohol while presenting.

One of the counter arguments to presenters consuming alcohol during presentations is that when you are presenting you are representing the conference. The conference wants you to be professional and create an environment that represents that during your talk. Fair enough, but why is it unprofessional?

This sequence of events has me wondering: what is professionalism in reference to presenting at Postgres Conferences? It is certainly not appropriate to be intoxicated while presenting at a professional conference, but that isn’t the question. The question is: why is it inappropriate for an adult to make a legal choice to take a nip or sip beer (or wine) during a presentation? Why is that more unprofessional than not wearing a tie or button up shirt, or wearing shorts or a kilt?

Professionalism is subjective.


In my opinion, my obligations to the audience are:
  • I must care about the content.
  • I must deliver what I say I will deliver.
  • I must be honest with the audience about my level of experience in the subject.
  • I must be honest about my opinions on the subject.
  • I must be a genuine version of me, minus the swearing.”
I fail at “minus the swearing” but the rest are spot on and should be our focus.

If you do not want presenters to consume alcohol during their presentations, then add it to your Code of Conduct. If it’s not in your Code of Conduct, then let adults take responsibility for themselves and present the best content possible for our community, in whatever way necessary.

Rock on and @amplifypostgres!

Disclaimer: I am writing this opinion as a frequent presenter, not as the Co-Chair of the most electrifying Postgres Conference in the world.


Joshua D. Drake     October 27, 2017