Joshua D. Drake Blog Posts

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

Image result for hyatt regency columbus ohio

PGConf US, in partnership with Ohio Linux Fest, is pleased to announce the schedule PGConf Local: Ohio is now available.

The inaugural PGConf US Local: Ohio Conference (PGConf Ohio) will be held September 29th - 30th at the Hyatt Regency Columbus Ohio (350 North High Street Columbus, Ohio, USA43215).

This two day, single track conference is a perfect opportunity for users, developers, business analysts, and enthusiasts from Ohio to amplify Postgres and participate in the Postgres community.


Conference Schedule:


Image result for bruce momjian
Mastering Postgres Administration: Bruce Momjian

Image result for Joshua D. Drake postgres

Conference speakers receive complimentary entry to the breakout sessions on September 30th as well as attendance to Ohio Linux Fest as well. The half-day training options on September 29th are separately priced sessions. As a nonprofit event series, funding is currently not available for speaker travel and lodging accommodations.


Sponsorship Opportunities
The PGConf US Local series is supported by its generous sponsors: Diamond Sponsor Amazon Web Services and Platinum Sponsors Compose, 2ndQuadrant, and OpenSCG. Please contact us if you are interested in joining our wonderful sponsors for Ohio or National!

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

The PGConf Local series partners with regional Postgres and open source groups to bring dynamic and engaging Postgres related content and professional training experiences to local communities. Host cities of 2017 include Philadelphia, Ohio, Seattle, Austin, and Cape Town, South Africa, with more locations to follow.

Contact: organizers@pgconf.us
Joshua D. Drake     August 30, 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

PGConf US and Austin PUG organized a PGConf Mini last night. It was three presentations over the evening. We had good attendance and excellent community participation. The highlight of the evening was PGConf US Co-Chair Jim Molgendski's presentation, "Top 10 Mistakes When Migrating from Oracle to PostgreSQL".

We tried something new this time around. We utilized Twitter's Periscope capability to live stream his presentation. It wasn't perfect but it was our first time and we are looking forward to utilizing the platform more in the future.

Click here to watch "To Mistakes When Migrating From Oracle to PostgreSQL", and then submit a presentation to one of our upcoming conferences:


PGConf US 2017 - 2018 
  • Diamond Sponsor: Amazon Web Services
  • Platinum Sponsor: OpenSCG

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

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




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

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

PostgresConf US 2018 is in 9 days. Here is the obligatory "Buy your tickets" reminder! If you look around (a Google search of Gold sponsor Google Cloud is a good place to start) you will find a lot of discount codes.

In 2017 we launched a community wide effort to better recognize contributors for not only the conference but the wider Postgres Community. We continued this effort in 2018 and are pleased to have many speaker profiles available, with more being published every day:

As one of the Chairs of PostgresConf, I am honored by the resounding support from sponsors, speakers, and volunteers to help create a fantastic event for all attendees. It has been a pleasure working toward the common goal of creating a global, non-profit, Postgres Conference series.
 
 
 
 

The PostgresConf team wanted to provide some information on the performance of PostgresConf US 2018 and events over the past year, as well as potentially answer some pending questions. Ultimately our goals are about people, which is why our motto is, "People, Postgres, Data." With each event we hold, each talk we accept, and how we train our volunteers, we make sure people (the benefit for and to), postgres, and data are considered and included. If there is no benefit or consideration to the growth of people, it is not an option.


With that in mind, please read on to see how our focus on people, Postgres, and data had an impact on the community over the last year.

Since PostgresConf US 2017 we have had events in:
  • Philadelphia 
  • Ohio (in combination with Ohio Linux Fest) 
  • South Africa 
  • Seattle 
  • Austin 
  • Jersey City (PostgresConf US 2018) 
  • Nepal 
All of these events are non-profit and volunteer organized.





PostgresConf US 2018


Logistics


  • Days: 5, 2 for training, 3 for Breakout sessions and summits
  • Official Attendance #: 601
  • Content: Over 207 sessions submitted
  • Sessions: Over 108 sessions provided 


Partner Support (Sponsors): 28


We had a record level of support from partners this year and due to this support we are going to be forced to find a new venue for next year. Our Jersey city location no longer has the capacity to hold us. This will increase costs but initial indications are that our partners understand this and are willing to support us financially to help continue the success of our efforts and keep costs reasonable for attendees.


Diversity


This year we were able to work with Women Who Code NYC. They provided many volunteers and we provided them with the ability to experience some of the best Postgres based content available, at no charge. We expect great things from this budding relationship in the future.


Professional Growth


We held a Career and Talent Fair. A dozen companies were present to connect with potential employees.

We also held a surprisingly well attended speed mentoring session for potential employees (Especially helpful for many of the WWC) on resumes and interview practices.

Leadership


This year saw the continued elevation of our primary leadership: Viral Shah, Lloyd Albin, Amanda Nystrom, and Debra Cerda. They continued to increase their presence and responsibility within the conference and dedicated hundreds of hours voluntarily to the growth of people. Our international members have also increased their leadership roles with our on-the-ground teams in South Africa and China.


Summits



We had our standard Regulated Industry Summit but also a Greenplum Summit. As I am sure you are aware Greenplum is an Open Source, Postgres based MPP database. They were by far the most popular booth in the entire conference and their summit was very well attended. The relationship with Pivotal and the success of the Greenplum Summit allowed us to learn new ways to bring together the entire Postgres Ecosystem. We expect to run a minimum of 3 more summits at PostgresConf US 2019.



Contribution


We were able to have several excellent (and long) meetings with leaders of Pivotal, Microsoft, Google, and Amazon on how they can begin contributing more back to Postgresql.org. All of them expressed a deep drive to contribute and a desire to learn more about the core community. Of particular note is Google, who would like to contribute the following back to the community:

https://github.com/google/pg_page_verification

We discussed with them the process and various changes they would need to make (license and code style, etc.). We also educated them on the PostgreSQL.Org rigorous review process.

Microsoft is reviewing how they can contribute but they showed an interest in build farm nodes, professional technical writers to help with docs, and potentially code contribution to our Windows port.

International Collaboration

The Chinese Open Source Promotion Union launched the Chinese Postgres Association. We invited them to PostgresConf US and introduced them to the United States Community. We expect great things from the Chinese community in the future.

Future


As we continue to build up our on-the-ground teams, we will likely hold less events in the U.S. this year. We will instead be focused on a smaller number of events in the U.S. and adding events in China and Europe. We have had an amazing amount of support from the Chinese community and the current goal is 1000 attendees for that conference.

Our current plan of events for the U.S. are


  • San Jose (October 2018) 
  • Philadelphia 
  • PostgresConf US (Manhattan) 

Future International Events


  • October 2018. 
  • Spring of 2019. 
  • Spring of 2019. 

This may change as we are actively recruiting on-the-ground teams to help us grow the community.

Collaboration


Our goal is collaboration and growth with other PostgreSQL community and Ecosystem efforts. We want to allow each potential community member to find a home. A place that they feel positive about contributing to the community as a whole. As we continue to grow as a community, it is vital to recognize that each member has their own needs, desires, and return on investment requirement (professional or personal) that they are seeking.

Tidbits of note



On DBEngines PostgreSQL is the 4th most popular database but the significance is that of the other 3, we are the only ones that are growing in popularity. 
Joshua D. Drake     May 07, 2018