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.

Join the fantastic and growing Postgres community in Cape Town, South Africa for a single day event on October 3rd, 2017! The event is being hosted by fellow Postgres advocates who travel from South Africa each year to attend our National Event in order to increase their knowledge of Postgres and be a part of the community. This year they are joining us and making a commitment to build out our International community and conferences!

• The CFP is open is open from now until August 25th. We will notify speakers by September 1st! Talks are subject to our presentation guidelines.

Local events are designed to bring comprehensive educational content and networking opportunities to the "local" Postgres community where the event is being held. They are perfect opportunities to show support for Postgres, find leads, and build relationships with other professionals and companies using and supporting Postgres.

Attendees of PgConf.US , if you haven't gotten your hotel room booked, now is the time! Our block ends on March 6th. Point your browser over here and book that room. While you wait for your email confirmation from the Westin, you can take some time to review the following talk from PgConf US 2015, ToroDB: a new, open-source, document-oriented, JSON database, built on Postgres.

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?

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!

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: Events PostgresConf Beijing CFP is open PostgresConf Silicon Valley CFP is open PGIBZ is being held at the end of June in Spain! Notable commits for Postgres 12 GSSAPI Encryption support Foreign Key support for partitioned tables Progress reporting for CREATE INDEX Generated Columns REINDEX CONCURRENTLY Upcoming People, Postgres, Data meetups NYC, April 24th: JSONB and When not to use JSONB  Salt Lake City, April 25th: Automated real time reporting of PG query logs Philly, April 25th, Awesome Automated APIs and Automagic REST Vancouver B.C., April 30: Monitoring and Managing Autovacuum  Subscribe to our community! (Announcements and Newsletters only)

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 :) .

It is with great pleasure that we announce the preliminary program for PGConf Local: Austin!