Joshua D. Drake Blog Posts

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

 Postgres Conference 2019


We’ve had a great response to our PostgresConf US 2019 call for proposals with over 170 potential presentations -- thank you to everyone who has submitted so far! As with what has become a tradition among Postgres Conferences, we are extending our deadline by one week to allow those final opportunities to trickle in!


We accept all topics that relate to People, Postgres, Data including any Postgres related topic, such as open source technologies (Linux, Python, Ruby, Golang, PostGIS).

Talks especially in high demand are sessions related to Regulated Industries including healthtech, fintech, govtech, etc., especially use case and case studies.

Interested in attending this year’s conference?

We’ve expanded our offerings, with trainings and tutorials open to everyone who purchases a Platinum registration. No separate fees for Mondays trainings (but it will be first come, first serve for seating).

Don’t forget that Early Bird registration ends this Friday, January 18. Tickets are substantially discounted when purchased early.

Register for PostgresConf 2019

Interested in an AWESOME international Postgres Conference opportunity? Consider attending PgConf Russia

PGConf Russia




Joshua D. Drake     January 15, 2019

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

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

 
Image result for postgresql
No year has been better for PostgreSQL or the Postgres Ecosystem than 2017. The continued adoption and growth of open source communities over the last 40 years shows a mature and strong ecosystem. It is true what they say, "Middle age is the best time of your life." Here are just a few of the great results of 2017:
  • Amazing work from PostgreSQL.Org with the release of v10 which brought much sought after technologies such as native table partitioning, integrated logical replication, and mature support for federated tables.
  • Pivotal announced multi-cloud support for their Open Source, BigData, MPP Postgres variant Greenplum.
  • Increased support and features from Cloud Industry heavy weights AWSCompose.IO, and Microsoft. Microsoft released Azure Database for PostgreSQL, Compose increased their high availability options, and AWS announced the availability of Amazon Aurora with PostgreSQL compatibility.
  • Enterprise Consulting and Support continued to grow with support from PostgreSQL.Org Major Sponsors 2ndQuadrant and OpenSCG.
2017 was also the year we saw the launch of the International Postgres Conference, PostgresConf. The PostgresConf project is a globally aware, ecosystem centric conference focused on People, Postgres, Data. The project organized more events this year than any other Postgres Advocacy and Education project. In the United States there was PGConf US (now PostgresConf US), Austin Mini, Philadelphia, (2) NYC Minis, Seattle, and finally a full Austin event. The project also hosted PostgresConf South Africa and has several International events planned in 2018.
 
The PostgresConf International efforts wouldn't be possible without the fundamental support of the community and our ecosystem partners:
 
 
 

We have nothing but confidence in the continued growth of PostgreSQL and the Postgres related ecosystem through 2018. Thank you to the PostgreSQL.Org community, our ecosystem partners, and the global Postgres Ecosystem community; without you our efforts would not continue to succeed as a volunteer organized, non-profit Postgres conference. We are looking forward to a fantastic 2018, centered on People, Postgres, Data.


 
 
Joshua D. Drake     January 08, 2018

PGConf US in partnership with the Austin PostgreSQL User Group (AUSPUG) is pleased to announce that the call for papers for PGConf Local: Austin is now open.


AUSTIN, June 28, 2017 -- The inaugural PGConf US Local: Austin Conference (PGConf Austin) will be held November 3 - 4, 2017, at the Norris Conference and Event Center (2525 W. Anderson Ln #365, Austin, TX 78757) located in northwest Austin.


This two day, multi track conference is a perfect opportunity for users, developers, business analysts and enthusiasts from the Southwest to amplify Postgres and participate with the Postgres community.
The Call for Papers for PGConf Austin is now open, and presentation proposals can be submitted at https://pgconf.us/conferences/Austin2017

The call for papers for PGConf Austin will be open until Sunday, August 20, 2017, and speakers will be notified of acceptance/decline no later than Monday, August 28, 2017. Registration for PGConf Austin will also open August 28.

Conference Schedule:
  • Friday, November 3, 2017: Half-day Trainings with Postgres experts
  • Saturday, November 4, 2017: Breakout Sessions (lunch and coffee break provided)


Conference speakers receive complimentary entry to the breakout sessions on November 4 -- the half-day trainings are separately priced sessions. As a nonprofit event series, funding is currently not available for speaker travel and lodging accommodations. Everyone is encouraged to submit a talk or training to the first PGConf supported nonprofit educational events in Texas, and join the growing PostgreSQL community.
Sponsorship Opportunities
PGConf Local series is supported by its generous sponsors, including Diamond Sponsor Amazon Web Services and Platinum Sponsors 2ndQuadrant, Compose, and OpenSCG, as well as Media Sponsor AmplifyPostgres. Business leaders and companies interested in sponsoring PGConf US nonprofit events can view the Conference Prospectus .


About PGConf US:
PGConf US is a nonprofit conference series with a focus on growing the Postgres community through increased awareness and education of Postgres. PGConf US is known for its highly attended national conference held in Jersey City, New Jersey, each year, and has expanded to a local series for 2017.


The PGConf Local series partners with local Postgres and open source groups to bring dynamic and engaging Postgres related content and professional training experience to their local communities in major metroplexes. 2017 host cities include Philadelphia, Seattle, and Austin, as well as Internationally in South Africa with more locations to follow.


Media Contact: organizers@pgconf.us

Joshua D. Drake     June 28, 2017

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








  1. https://www.socialworktoday.com/archive/072417p32.shtml
Joshua D. Drake     May 19, 2021     eds postgresql



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



In review of these numbers two things will probably jump out at you:
  1. Venue and F&B of 238,000.12
  2. Net Revenue of 202,201.62
Yes, we spent almost 250,000.00 dollars on the venue and food and beverage. In fact, the Food and Beverage alone was over 135,000.00 dollars. 

We were fortunate to have very strong ticket sales as well as partner support through Sponsorships. This support will allow us to not only meet our financial requirements for PostgresConf Silicon Valley 2018 but will help us make our financial requirements for our European, Chinese, and US conferences in 2019. We are also hoping to set aside more money for our popular diversity and professional development initiatives.

The Chairs would like to thank all our organizers, volunteers, partners and attendees for helping us continue advocacy of People, Postgres, Data!


Joshua D. Drake     May 25, 2018

People, Postgres, Data,

Due to the health risks and travel restrictions created by the Coronavirus we unfortunately have to cancel Postgres Conference 2020 which was to be held at the Marriott Marquis on March 23rd, 2020 thru March 27th, 2020.

We want to thank all of our attendees, partners and volunteers for all the hard work we all put in to try and pull this event off. Sadly, the stars were not aligned this year. We now focus our efforts on Postgres Conference Silicon Valley 2020 and our Digital Events

Thank you all for your patience and support,

Postgres Conference Chairs

Joshua D. Drake     March 12, 2020




The presentation includes an introduction and setup for consul as the means of providing highly available PostgreSQL in local and geographically disparate data centers or cloud providers. The presentations includes:

*) Introduction to consul and its architecture
*) Setup of a single consul cluster
*) Setup for a few sample database instances (OLAP and OLTP)
*) Firewall requirements
*) Integration with bind, djbdns, and dnsmasq
*) Setup geographic failover to two different data centers and cloud providers
*) Various Best Practices tips and suggestions
*) Q&A

Joshua D. Drake     April 25, 2017