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?

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

PGConf US in partnership with SeaPug is pleased to announce that the call for papers for PostgreSQL Conference US Local: Seattle is now open. 

National Diamond Sponsor

The call for papers will be open from May 16, 2017 until July 2, 2017. Speakers will be notified of acceptance/decline no later than July 8.

The two track, two day conference is a perfect opportunity for the Vancouver, B.C., west coast, and Rocky Mountain regions to join the PostgreSQL community and increase their knowledge.

National Platinum Sponsor

Breakdown of the Conference Layout: 

• August 11th: Training
• August 12th: Breakout Sessions 

All selected presenters will receive free entry to the breakout sessions (trainings are extra). There are no grants for travel and accommodations. We encourage everyone to submit a talk or training to one of our very first PostgreSQL Conference US Local events and be a part of growing the PostgreSQL community.

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.

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

• What is high cardinality, and how do time-series databases like InfluxDB and TimescaleDB compare?

• 11 Things to Know about Databases and Postgres in Containers

• PostgreSQL security: a quick look at authentication best practices [Tutorial]

• Distributed PostgreSQL on a Google Spanner Like Architecture - Storage Layer

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:

 

• Outflux (Outflux -> TimescaleDB migration tool)

• Yugabyte v1.2.4 (Apr 02, 2019), Distributed SQL

• Postgres Checkup 1.0, Automate checking on Postgres health

• PgCLI v2.1.0, A feature-full command line client for Postgres

Join our community

• News and Announcements

Upcoming Events

• Postgres Ibiza

• PostgresConf Beijing

• PostgresConf Silicon Valley

• Silicon Valley Postgres Meetup

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.

With 2020 firmly in the rear view mirror, it is time to look forward and down the highway of 2021. The organizers of People, Postgres, Data have gathered over chat, email, phone, and even a few socially distant, in-person events to determine a strategy for continuing as the most influential and positive community for all things Postgres related.

Sad face

The goal is to resume in-person events. However, out of concern for the health and comfort of our global community, we have made the decision not to host any in-person events until Q4 of 2021. We are prepared to wait until 2022 if that is what the health officials recommend. We know that many will find this news disappointing and we are working diligently to ensure that the health and education of our community is the top priority.

Happy face

We are continuing our popular webinar series, adding new presenters with pertinent content for all of our attendees. We will be adding more professional development and data problem solving topics to our library, and we will no longer be limiting education to just Postgres, as many data and human problems are neutral in the particular platform we happen to enjoy. If there’s a topic you’d like to present or see, we’d love to hear from you!

RSVP for upcoming scheduled events

• January 26, 1pm ET: All we need to work with SQL is SQL
• January 27, 1pm ET: PostgreSQL Forks and Knives
• February 3, 2pm ET: Postgres for SQL Server Users
• February 4, 1pm ET: Configuring PostgreSQL for Faster Analytic Query Performance
• February 23, 1pm ET: Blockchain as a Database

Ecstasy 

Postgres Conference 2021: Digital will be happening in May of this year! An overwhelming feeling of great happiness and excitement has our dopamine pumping, and the whole People, Postgres, Data team is basking in it. 

 

As an all digital conference, we will offer a similar environment to what our community has come to expect: best in class content, professionalism, and top-tier educational opportunities for all who attend! Keep your eyes peeled over the next few weeks for more information on speaking opportunities and how to attend!

Join us for a special presentation with PostgreSQL experts who will be in town for DataLayer 2017.

Food and refreshments will be provided, so please be sure to RSVP.

Thank you to OpenSCG for sponsoring our food and soft drinks, and fibercove for hosting us! Beer sponsor TBA.

• The event starts at: 6 pm 
• Networking and food/drink : 6:15 pm 
• Announcements and updates: 6:30 pm   

Presentations:
• "Softlayer vs RDS/AWS: A price to performance perspective" - Joshua D. Drake, Command Prompt, Inc.

• "PostgreSQL on Debian and apt.postgresql.org" - Dr. Michael Meskes, CEO of credativ (http://www.credativ.com/)

• "Top 10 Mistakes When Migrating From Oracle to PostgreSQL" -- Jim Mlodgenski, CTO of OpenSCG
 
About our Speakers: 

Joshua D. Drake of Command Prompt, Inc. (https://www.commandprompt.com/), is a PostgreSQL Consultant who has consulted on PostgreSQL since Postgres95. Throughout his PostgreSQL career he has performed a variety of functions within the community including releasing an O'Reilly book on PostgreSQL, as well as being part of the sysadmins and advocacy teams He ran a biannual conference series dedicated to PostgreSQL from 2007 - 2011. He is a former Director for SPI (the non-profit for PostgreSQL.org). Drake is also a Founder of United States PostgreSQL, as well as a co-organizer and Chair of PGConf US.

Dr. Michael Meskes is President and CEO of the credativ Group, an industry leader in free software services with offices in five countries. Its Open Source Support Centers employ leading members of a number of Open-Source projects. He has been Open-Source developer for twenty years working on different Open-Source projects among which Debian and PostgreSQL are most widely known. He also has done a lot of Open-Source related presentations on all sorts of events doing a lot of Open-Source evangelism.

Jim Mlodgenski is CTO of OpenSCG, a leading enterprise open source services company, with a central focus on PostgreSQL. He has been part of the PostgreSQL community for over a decade, as an architect and sales engineer. He is a Director for the U.S. PostgreSQL Association, as well as an organizer of the Philly PostgreSQL User Group and a Co-organizer of the NYC PostgreSQL User Group. He Is also a co-organizer of PGConf US, the largest PostgreSQL conference in the U.S.

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

Efficiently and Safely Propagate Data Changes Without Triggers!