Joshua D. Drake Blog Posts

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



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

We are having yet another PGConf Mini in NYC. The event is scheduled for December 14th, 2017 and Work Bench is hosting:

 
 
The event is part of the PGConf Mini series and is free to attend. The PGConf Mini series works directly with user groups and external communities to organize events for the local community. The events are held as a larger meetup style event with networking opportunities and up to 4 presentations. The current agenda for the latest PGConf Mini: NYC is:
 
Agenda: 
 
• 6:30 - 7:00: Jonathan Katz, (TBD), Postgresql Contributor and PGConf Chair Emeritus

Efficiently and Safely Propagate Data Changes Without Triggers!

 

Prior to PostgreSQL 9.4, the primary way to distribute data-driven changes across multiple tables was to use triggers. While triggers guarantee that these changes will be propagated, they can have a significant impact application performance, both technically and with development time (see: "debugging"). PostgreSQL 9.4 introduced logical decoding, which provides a way to stream all changes in a database to a consumer. Using a logical decoder, you can read all changes that are made in a table into your programming language of choice to perform many tasks: cache invalidation, data propagation, submitting changes to remote services, and more. Many PostgreSQL drivers, such as psycopg2 and JDBC support the logical replication protocol, which lets you easily stream your database changes to be manipulated using your favorite programming language. This talk will demonstrate how you can setup logical decoding for your application, look at architecture strategies for working with a logical decoder, and look at a case-study that shows how using logical decoding led to a big performance boost over a similar trigger-based system.
 
• 7:00 - 7:30:  Kevin Jernigan, Senior Product Manager, Amazon
Technical Architecture of Postgres Aurora 
 
Amazon Aurora is a cloud-optimized relational database that combines the speed and availability of high-end commercial databases with the simplicity and cost-effectiveness of open source databases. The recently announced PostgreSQL-compatibility, together with the original MySQL compatibility, are perfect for new application development and for migrations from overpriced, restrictive commercial databases. In this session, we’ll do a deep dive into the new architectural model and distributed systems techniques behind Amazon Aurora, discuss best practices and configurations, look at migration options and share customer experience from the field. 
 
• 7:30 - 8:20: Joshua (JD) Drake POSTPONED due to flight cancellation)
The Power of Postgres Replication, Postgres Expert - Lead Consultant Command Prompt, Inc and Co-Chair PGConf!
 
With PostgreSQL v10 a new replication engine has come to town. Let's explore Postgres Logical Replication, how to use it, optimize it and let it best fit in with your organization. We will also discuss its interactions with external tools as well as Binary Replication and features such as Hot Standby. 
 
 
 
 
Joshua D. Drake     November 20, 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

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

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

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

Pivotal Sponsor Highlight Blog for PostgresConf 2019

 

Written by:

Jacque Istok, Head of Data, Pivotal

 

1. Greenplum has its own community; what do you hope to achieve by joining the Postgres community and PostgresConf?

Both interest and adoption of Postgres have skyrocketed over the last two years, and we feel fortunate to be a part of the extended community. We have worked very hard to uplevel the base version of Postgres within Greenplum to more current levels and to be active in the Postgres community. We see Greenplum as a parallel (and analytic focused) implementation of Postgres, and we encourage the community to continue to embrace both the technology and the goal of the Greenplum project, which is Postgres at scale.

 

2. Are you planning to provide any new tech (PG features, etc.)?

This year we plan to announce several new things for both Greenplum and Postgres. We’re introducing new innovations in our cloud offerings in the marketplaces of AWS, Azure, and GCP. We also have major news about both our natural language at-scale analytics solution based on Apache Solr, and our multi-purpose machine learning and graph analytics library Apache MADlib. The next major release of Greenplum is a major focus as well, differentiating Greenplum from each of its competitors and bringing us ever closer to the latest versions of Postgres.

 

3. Are there any rising stars in the community you’d like to give props to?

While it seems a little self-serving, I would like to take the opportunity to give props to the Pivotal Data Team. This team is a 300+ worldwide organization that helps our customers, our prospects, and the community to solve real world and really hard data problems—solved in part through Postgres technology. They all attack these use cases with passion and truly make a difference in the lives of the people that their solutions touch. I couldn’t wish to work with a finer group.

 

4. What is the number one benefit you see within Postgres that everyone should be aware of?

The number one benefit of Postgres is really its flexibility. This database chameleon can be used for SQL, NoSQL, Big Data, Microservices, time series data, and much more. In fact, our latest analytic solution, MADLib Flow, leverages Postgres as an operational engine. For example, Machine Learning models created in Greenplum can be pushed into a restful API as part of an agile continuous integration/continuous delivery pipeline easily and efficiently—making Postgres the power behind what I still like to think of as #DataOps.

 

5. What is the best thing about working with the Postgres community?

 

I deeply admire the passion and consistency of the community behind Postgres, constantly and incrementally improving this product over decades. And because Greenplum is based on Postgres, we get to interact with this vast community of talent. We are also able to more seamlessly interact with ecosystem products that already work with Postgres, making the adoption of Greenplum that much easier.

 

6. Tell us why you believe people should attend PostgresConf 2019 in March.

 

PostgresConf is going to be awesome, and I can’t wait for it to start! With Pivotal, Amazon, and EnterpriseDB headlining as Diamond sponsors, Greenplum Summit (along with multiple other summits), and high-quality speakers and content across the board, this year’s PostgresConf promises to be bigger and better than ever and surely won’t disappoint.

 

We’re thrilled to be back to present the second annual Greenplum Summit on March 19th at PostgresConf. Our theme this year is “Scale Matters”, and what we’ve seen with our customers is that every year it matters more and more. Our users are part of organizations that are generating tons of data and their need to easily and quickly ingest and interrogate all of it is paramount. This is true even more now than ever before as the insights that can be found not only help differentiate them from their competitors, but are also used to build better products and increase customer loyalty.

 

The day will be filled with real-world case studies from Greenplum users including Morgan Stanley, the European Space Astronomy Centre, Insurance Australia Group, Purdue University, Baker Hughes (a GE company), Conversant, and others, plus presentations and deep-dive tech sessions for novices and experts alike.

Joshua D. Drake     February 14, 2019

Congratulations

Henrietta Dombrovskaya, Diversity, Equity, and Inclusion member for PostgresConf as well as Chicago Postgresql organizer nominated for Technologist of the Year!

 

Career Opportunity

A large, well known media company is seeking a Senior Level PostgreSQL Engineer and Architect. This is an on-site engagement, however the company is known to be lifestyle friendly with reasonable working hours, good pay, and benefits. Specific talents requested are the ability to mentor. The location is Seattle, WA. If you are interested in this position please contact randy@neuringerco.com with your resume.

Great content

Extension Highlight

We wanted to highlight some of the fantastic work that is being done by the ecosystem with Postgres Extensions. Although the base of Postgres is the amazing and extensible PostgreSQL, a lot of users don’t realize that Postgres has the feature they are looking for, if only they were to look to the ecosystem.

Notable Extensions:

  • pgaudit : The goal of pgAudit is to provide PostgreSQL users with the capability to produce audit logs often required to comply with government, financial, or ISO certifications.

  • pg_credereum : pg_credereum is a PostgreSQL extension that provides a cryptographically verifiable audit capability for a PostgreSQL database, bringing some properties of blockchain to relational DBMS.

  • H3-pg : PostgreSQL bindings for H3, a hierarchical hexagonal geospatial indexing system.

Postgres can do what?

There are a ton of Postgres compatible features out there. Some of them are overlooked core features and some of them require installing a different version of Postgres. Here are a few examples:

 

  • TimescaleDB: Time series data management with Postgres

  • YugabyteDB: Globally Distributed database with PostgreSQL compatibility

  • Postgres-XL: Horizontally partitioned PostgreSQL

  • Agensgraph: Graph capabilities with Postgres

  • PG-Strom: GPU accelerated extension for Postgres 

 

Upcoming Education and Networking opportunities:

 

Joshua D. Drake     August 07, 2019