Joshua D. Drake Blog Posts

PostgresConf 2019: CFP and Early Bird closing soon

PostgresConf hopes everyone had a great holiday season and we hope everyone has a fantastic 2019.

With January upon us, we start conference season. This year, PostgresConf 2019 will be in NYC at the Sheraton New York Times Square March 18-22, 2019.

If you have a story about lessons learned with Postgres, a cool feature that you've found a creative way of using, or just some practical knowledge you'd like to share with your fellow Postgres users, submit a talk. Remember, there are many people who are new to Postgres, so introduction levels talks are welcome. The CFP ends this Friday so get your talks submitted soon at:
https://postgresconf.org/conferences/2019#callforpapers

Also, the Early Bird window for PostgresConf 2019 will be ending next Friday, January 18. This tickets are pretty substantially discounted if you purchase them early. On top of the Early Bird discount, for being a member of the NYC Postgres User Group, there is a promo code for an additional 15% off. Just use the code 2019_PUG_NYC when buying your tickets.
Lastly, if you are already in the NYC area we look forward to seeing the community at the Winter Party on the 10th!
We hope to see you at PostgresConf 2019 and remember:



Joshua D. Drake     January 09, 2019

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

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

PostgresConf US 2018: Schedule almost granite!

With more than 200 events submitted and approximately 80 slots to be filled, this has been the most difficult schedule to arrange in the history of PostgresConf. By far, the majority of content received we wanted to include in the schedule. It is that level of community support that we work so hard to achieve and we are thankful to the community for supporting PostgresConf. There is no doubt that the number one hurdle the community must overcome is effective access to education on Postgres. The US 2018 event achieves this with two full days of training and three full days of breakout sessions, including the Regulated Industry Summit and Greenplum Summit.


For your enjoyment and education here is our almost granite schedule!

See something you like? Then it is time to buy those tickets!

This event would not be possible without the continued support from the community and our ecosystem partners:

Joshua D. Drake     February 22, 2018

Community member profile: Joshua Brandt & BrandtVX

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

PGConf US welcomes 2ndQuadrant as a Platinum sponsor

After National 2017, the PGConf US team decided to take a long hard road to bring the best in educational content and advocacy to the entire Postgres ecosystem. Today, we welcome 2ndQuadrant as a Platinum sponsor and thank them for helping us with our year over year projects.


2ndq logo color no cross

It is sponsors like 2ndQuadrant that are allowing us to achieve our goal of having not only our National event but Philly, Seattle, and Austin all within 2017. We also have other education and advocacy initiatives that continue to develop include webinars, community profiles, and e-training. Stay tuned for more information on those!

Other PGConf US news:


Joshua D. Drake     June 29, 2017

PostgresConf US 2018: CFP ends on January 22nd

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

What time you ask?

The time to join the largest Postgres Conference in the world by submitting a talk or training to PostgresConf US 2018!

We want to set the world stage for what a Postgres and Data conference should look like with quality people, quality content, and lots of interesting things about data.

Your window is short; the CFP closes on Monday at midnight. That means no last minute, witching-hour submissions!


PostgresConf.Org would not be possible without our speakers, attendees and sponsors. 

Diamond: Amazon Web Services, Pivotal
Platinum: Compose.IO, 2ndQuadrant, OpenSCG, Microsoft
Joshua D. Drake     January 18, 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

People and Postgres: April 30th, 2019



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

Presenter Professionalism at Postgres Conferences

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