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

Rescheduled: PGConf US Local: Seattle and PGConf US Local: Austin

Community,


The Chairs of PGConf US have rescheduled the Seattle and Austin Local events. After much deliberation we believe moving the events to a weekday format later in the year will offer a better opportunity for those who wish to attend.

New dates:
  • Seattle: November 13th and 14th, 2017
  • Austin: December 4th and 5th, 2017
The CFP for Seattle is closed but Austin is still open!

People, Postgres, Data

Joshua D. Drake     August 08, 2017

2017, the year PostgresConf and Postgres reached the masses

 
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 AWS, Compose.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

Top 10 Mistakes When Migrating From Oracle to PostgreSQL

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

Community member profile: Darren Armani & Vertex Enterprise 






Why did you attend PgConf US?

Our company is exploring the use of PostgreSQL as an additional DBMS choice to support Vertex Enterprise, our tax technology platform. Attending the conference offered me an opportunity to immerse myself into a variety of topics around PostgreSQL, as well as the chance to interact with other users to tap into their experiences.


Tell us a little bit about your project or how you use PostgreSQL:


Vertex Enterprise is a global tax management end-to-end solution that integrates all tax processes with Enterprise Resource Planning (ERP) and business intelligence (BI) systems on a single platform using a tax performance engine.   The solution is a blend of technologies that surround a Java based processing and calculation engine. This includes rich UI's, import, export, business intelligence / reporting, and big data integration. The foundation of our database leverages a multi-dimensional database structure, as well as other structures whose design varies based upon the needs of a particular function so that we can optimize performance. (ie. import/export/reporting).

The official brochure provides a high level overview of the capabilities and interfaces that our DBMS must support.  


Why did you chose PostgreSQL for your project?


PostgreSQL checks many of the boxes that we are looking for in our consideration of an additional DBMS option.


Some of these include:


* Performance
* Lower cost
* Multi-tenancy support 
* Suitable for deployment on premise, in a hosted environment, and in the cloud
* Industry acceptance
* Ease of administration on locally administered instances
* Features characteristic of an enterprise strength database (auditing, partitioning, replication, procedural language support)


This was your first PGConf US, was it a last minute decision? Do you think it was worth it? If so, why?


The conference was on our radar since the beginning of the year, and it exceeded expectations. Listening to and interacting with actual contributors to the product is not something you have the opportunity to do at many conferences. The sessions covered a variety of topics around PostgreSQL that were of interest (performance, tuning, feature discussion, lessons learned, cloud deployment options, optimization, etc).


Would you attend PgConf US again?


Yes, definitely. 


Are you interested in contributing to the community and if so, in what fashion?


My "day job" keeps me pretty busy, but as far as sharing our experience with PostgreSQL, I am willing to contribute in that way :) .
Joshua D. Drake     April 10, 2017

Greenplum, the Postgres Community and PostgresConf

 
 

As part of the countdown to PostgresConf US 2018, learn more about the engaging content and our Diamond and Platinum sponsors for this year in our Sponsor Spotlight Series.

Jacque Istok, is the Head of Data for Pivotal, one of our Diamond Sponsors for PostgresConf US 2018. Pivotal is hosting the first annual Greenplum Summit at PostgresConf US 2018, with lots of great Greenplum and Postgres-related content. Read what Jacque has to say bout Greenplum and Postgres, as well as why to attend the Greenplum Summit: 

Greenplum is an Open Source variant of Postgres; what benefits do you bring to the table over vanilla Postgres?

Postgres is a powerful ORDBMS, but as your data scales, the only way to keep up is to buy bigger and bigger machines to run on. It suffers from the same problems that all SMP databases do: you can only get as big as the machine you’re running on.

With Greenplum you can put a subset of your data on a Postgres database on one reasonably-sized machine, and another subset on a second machine, and so on. All of your users and applications can then query one of these Postgres databases as if all the data was in a single location - making your data scale limitless. Greenplum manages the distribution, data shuffling, and querying of all of your data across a magically sharded implementation of Postgres databases.

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

The Postgres community represents some of the most passionate and knowledgeable creators, developers, and users of database technology of our time. We believe that the combination of Postgres and Greenplum becomes the software equivalent of what Oracle Exadata purported to be: an all-purpose database that can do both transactional and analytical workloads across multi-structured data. Simply put, the Greenplum community is looking to join with the Postgres community to further the understanding and adoption of these technologies.

Do you have plans for cross pollination of technologies with the two open source projects?

Greenplum forked from Postgres over 10 years, circa Postgres 8.2. Greenplum 5.0 is based off of Postgres 8.3, with our next major release slated for Postgres 9.4 (current open source Greenplum is compatible with 9.0 as of this writing).

Likewise, we have Postgres committers working at Pivotal looking for opportunities to improve the Postgres code specifically for analytics. We are also ensuring that other projects related to Greenplum, like Apache MADLib, continue to be compatible with Postgres.

What challenges do you see working with the Postgres community as an open source fork?

The Postgres community is a long-running and very passionate group, and we want to be both collaborative and respectful in how we continue to grow our participation. We see the products as having synergies which complement each other very well, with some use cases that best fit Postgres, and others that best fit Greenplum. The use of either benefits the other as they both further adoption.

What would you tell a user who has a choice between Postgres and Greenplum about when they should use which system?

Postgres is a great ORDBMS that will scale to the performance of a single server. For analytical needs, being restricted to a small number of terabytes does not allow for the type of exploration that most organizations need. Because Greenplum is a Postgres compatible database, you can start out using Postgres and either convert to Greenplum underneath or leverage Greenplum alongside your Postgres systems (making data ETL a ton easier). This then makes the choice of which product to use for your particular use case clearer and clearer.

What is the number one barrier you see to contributing to the Postgres community?

The number one barrier we will have to contributing is not seeing the corresponding adoption of our technologies. We feel very strongly that both the transparency and removal of vendor lock-in make our open source commitment the only choice for users. I’m here to implore the community to embrace our technology with zeal and help us continue to drive more and more Postgres adoption in the world.

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

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.

Tell us why you believe people should attend PostgresConf 2018 in April.

PostgresConf is going to be awesome - with both Pivotal and Amazon headlining as Diamond sponsors - as well as the quality of speakers and their content. I wouldn’t miss it for anything.

We’re thrilled to organize the first annual Greenplum Summit at PostgresConf. Greenplum co-founder, Scott Yara, will give a keynote on April 18th relating to how data tells the story at the organizations that we help enable (#DataTellsTheStory), and his journey from SMP to MPP. Greenplum Summit on April 19th will be a full day packed with with great use case sessions and tech talks for novices and experts alike.

Check out the full schedule for PostgresConf US 2018, and buy your tickets soon!



Joshua D. Drake     March 26, 2018     pivotal Greenplum postgres postgresql

Community Profile: Alex Tatiyants and Pev

We caught up with Alex Tatiyants after finding out about his Pev project. This is an awesome web based visual explain analyzer that is similar to the awesome explain.depesz . 

Tell us a little bit (one or two paragraphs) about your project or how you use Postgres: 

I created Pev (Postgres EXPLAIN Visualizer) to scratch my own itch. EXPLAIN generates a wealth of information, but isn’t easy to make sense of. I wanted to create a tool that helps me quickly diagnose problems with queries. Apparently, other people found it useful as well.


Pev plan


Why did you chose Postgres for your project? 


Postgres is a fantastic database: performant, mature, feature rich, and of course open source. And in addition to being a first rate relational database, it has very strong document store features as well.


Have you attended a PgConf US event or do you plan to? 

I haven't had a chance to attend PgConf.

Are you interested in contributing to the community further and if so, in what fashion? 

I don’t have any concrete plans at the moment.

Any closing comments? 

Thank you for your interest.
Joshua D. Drake     August 16, 2017

PGConf US Local: Seattle CFP reopened and three new tracks added!

Oh my goodness, Data Days!


When we rescheduled PGConf US Local: Seattle from August to November we did so due to attendee feedback. It was amazing - people didn't want to go to a conference on Saturday in August (I wonder why). I know, we should have known but it was a new model and we tried. We are extremely pleased with the results of the shift in schedule. The conference now takes place during "professional hours" on "professional days."

Image result for creative commons professional

Because of the shift and sponsor support we have added three new tracks, reopened the CFP, and created Data Days. The new tracks are: Big Data, AWS/Cloud, and Data Science. As these three Postgres content areas are Postgres independent we are also requesting that all communities within this realm submit to present. Let's turn PGConf US Local: Seattle into not only the best West Coast Postgres Conference but also the most highly integrated, heterogeneous data event in the Pacific Northwest.

CFP Dates:

  • Open until: 10/15/2017
  • Notification:  10/18/2017
  • CFP Link
Joshua D. Drake     September 19, 2017

CFP for PostgresConf Silicon Valley closes August 15th

You will want to mark your calendars folks on August 15th the Call for papers for PostgresConf Silicon Valley will close. That is just two weeks away!

So let's point your Firefox, Google Chrome, or Safari app to this link right here and get your presentation submitted.

This is the inaugural Silicon Valley conference and from the current submitted papers it is shaping up to be a fantastic event. We can't wait to see everyone and continue our mission of:




Joshua D. Drake     July 31, 2018