Blog

Welcome to "Cultivating DEI" , a series in which Postgres community members share their insight and experience about creating a more diverse and inclusive Postgres environment where all are welcome.

Recently I've been thinking a lot about relationships between the PostgreSQL community and the Database research community. To put it bluntly – these two communities do not talk to each other!

There are many reasons why I am concerned about this situation. First, I consider myself belonging to both of these communities. Even if right now I am 90% in industry, I can't write off my academic past. Writing a scientific paper with the hope of being accepted to the real database conference is something which appeals to me.

Secondly, we want to have quality candidates for database positions. Anyone who has tried recently to fill these positions knows that this is not an easy task. If you are looking at recent college grads, there are almost no chances that you can find somebody who has PostgreSQL experience. Here is where we face the other side of the problem.

The problem is not simply that scientists do not speak at the PostgreSQL conferences, and that PostgreSQL developers do not speak at academic conferences. The larger issue is that for many Computer Sciences (CS) students, their academic research and practical experience do not intersect. They learn about some incredible algorithms, and as part of their coursework they may suggest some enhancements to existing algorithms. They then practice their SQL skills with MySQL, which from my observations lacks so many basic features, that it can hardly be taken seriously as a data platform.

If students practiced using PostgreSQL, they would have a full-scale enterprise ready object-relational database -- not a "light" version, but a robust platform, which supports a multitude of index and data types, constraints, procedural languages and much more.

I've heard from several professors that "MySQL is okay for "learning SQL." I want to ask -- what does "learning SQL" mean? Is it just learning how to write a syntactically correct SQL? One contributing factor to the problem is that MySQL comes on each laptop by default, integrated with basic tools that allow building websites. It is integrated with Wordpress. There is no reason for PostgreSQL not to have similar support, but it is not in place.

This is particularly frustrating when you recognize the amount of database research was completed using Postgres, for Postgres or with help of Postgres; R-Tree and GIST indexes, for example. Also, the SIGMOD Test of Time Award in 2018 went to the paper "Serializable isolation for snapshot databases," which was implemented in PostgreSQL.

I know the answer to the question "why do they not talk?" Researchers do not want to talk at the PostgreSQL conferences, because those are not scientific conferences, and participation in these conferences will not result in a publication. Postgres developers do not present at the CS conferences, because they do not want to write long papers. Even if they do submit something, their papers are often rejected as "not having any scientific value." I have experienced this on multiple occasions.

I came across another example of "why” when I attended the ACM/SIGMOD conference in Amsterdam. I attended a compelling presentation on the problem of cardinality estimation over multi-join queries, that introduced new optimization techniques. The presenter mentioned that he had used Postgres to build the prototype. I was too far back in the room to ask my question, so I reached out via the conference website.

I asked the presenter why he didn't submit a patch. He replied that their approach was hacky, and it needs more work to think about adding it to Postgres. I've asked whether he would be interested in working on it with some PostgreSQL community members. His reply? "Not in the next two years, I've just received a post-doc position at Microsoft, so I can't do it for the next two years."

So yes -- I know the answer as to why these two communities historically do not communicate. However, I do not like or accept it. Perhaps we can talk about and resolve this problem together?!

Contributor Bio:

Henrietta Dombrovskaya is a database researcher and developer with over 30 years of academic and industrial experience. She holds a Ph.D. in Computer Science from University of Saint Petersburg, Russia. She taught Database and Transaction theory at the University of Saint – Petersburg (Russia), as well as multiple database tuning classes for both beginners and advanced professionals.

Her professional experience includes consulting for a number of government projects in Chicago and New York, and providing Data services in the financial sector, manufacturing, and distribution. She is a co-author, with B. Novikov, of the book “System Tuning”, BHV, S.-Petersburg, Russia. Her researches in overcoming object-relational impedance mismatch were publish in the Proceedings of EDBT 2014 Athens and ICDE 2016 in Helsinki. At Braviant Holdings she is happy to have an opportunity to implement the results of her research in practice.

Henrietta Dombrovskaya is a co-organizer of the Chicago PostgreSQL User Group and a member of the Diversity, Equity, and Inclusion Work Group for the Postgres Conference Series. She was recently awarded the 2019 "Technologist of the Year" award by the Illinois Technology Association. This award is  "presented to the individual whose talent has championed true innovation, either through new applications of existing technology or the development of technology to achieve a truly unique product or service."

Come as you are

The theme of Postgres Conference for 2020 is: Come as you are. We want everyone to feel welcome. You are welcome for your love of People, Postgres, Data and a desire to ascend beyond the box. It isn’t about your race, gender, sexuality, political affiliation, or love of blueberry flavored popcorn. It is 100% about you, the creativity and excellence that only you can bring to our community.

Postgres Conference 2020 CFP now open

We are actively seeking content for the largest Postgres Conference in the world, set to be held from March 23rd to 27th, 2020  at the Marriott Marquis, Time Square! Please submit your content here.

Postgres Conference Silicon Valley 2019

Postgres Conference Silicon Valley doubled its attendance, making it the largest Postgres  Conference on the West coast ever! We are very pleased to be able to bring so many community members together for education, fun, and ecosystem support!

 

Training

  • Postgres Conference is now offering live digital training throughout the year. Continuing on our mission of creating exceptional Postgres people, you can now not only register for pre-defined training but request specific training and we will connect you with a class! The current training options are:
    • PostgreSQL Performance and Maintenance
    • Finding and Fixing slow queries
    • Postgres + Kubernetes: yes it really is a match made in heaven
    • PostgreSQL Replication deployment and best practices
    • PgPool-II Performance and best practices

 

Register here: https://postgresconf.org/conferences/Postgres-Digital-Training-Series

 

Digital Events

We have free digital events coming up including topics such as Kubernetes, DistributedSQL, Backups, Postgis and many more. Coming up: 

Joshua D. Drake     October 02, 2019
Pivotal On Light

As part of the countdown to PostgresConf Silicon Valley, learn more about featured Partner Sponsor Pivotal, including their commitment to partnering with and contributing to the Postgres community.

Tell us about your commitment to the PostgreSQL Community.

For those who haven’t heard of us, Greenplum is PostgreSQL massively scaled specifically for analytics. We’ve optimized PostgreSQL for complex analytic queries on text, graph, geospatial, and structured business data.  Via free, open-source Apache MADlib, Python, and R libraries, Greenplum is also capable of in-database machine learning and deep learning, and in our latest version we support distributed execution of Keras/Tensorflow along with GPU acceleration.   Our blog highlights  everything that’s new in our latest version (6.0).

Moreover, we now also offer a commercially-supported version of open-source PostgreSQL based on v11. 

At Pivotal, every product we build is based on open-source, and we’re committed to the viability of the PostgreSQL community.  There are over 100 engineers at Pivotal that contribute to the community, and we’ve made a number of contributions to v11.  We’re currently working on contributions for things like a column store, parallel grouping sets, and improvements to PL/R performance.

You can join our very active community at Greenplum.org.

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

We’re excited to be part of one of the most successful, longest-running open-source projects.   We enjoy the camaraderie and solidarity of the community, and the willingness of participants to engage, share and collaborate.

We have a large community of PostgreSQL experts at Pivotal – we’ve been working with it for over 15 years – and we’re always interested in adding to it.  Please visit our careers page for more information!

Why is Postgres an ideal foundation to build on?

It’s open source, is proven by a large number of commercial deployments, and has an active community. The ecosystem and the many tools and extensions were incredibly valuable to help us accelerate innovation faster than we could on our own.  We plan to be part of this community for the long haul.

Why should you attend PostgresConf Silicon Valley 2019 in San Jose?

The PostgresConf events in general are great for learning and collaboration.  You can learn from people using Postgres to solve meaningful problems in production, and you make relationships that will last throughout your entire career.    If you haven’t been before, we heartily recommend that you join us here!

 See you at PostgresConf Silicon Valley 2019!

---

Bob Glithero, Head of Product Marketing for Pivotal Greenplum

info@pivotal.io

Bob Glithero     September 10, 2019

Summer is officially over (although the calendar says otherwise), the kids are back in school, the last three-day camping weekend of the season has passed, and we are staring right at PostgresConf Silicon Valley starting September 18th! Registrations for this fantastic event have already exceeded 2018 numbers and our training day is showing great success. 

Conferences

Digital Events

  • YugabyteDB Distributed SQL Webinars
    • A series of free webinars discussing technical opportunities with Distributed SQL. YugabyteDB is an Open Source, Postgres compatible Distributed SQL database.

News

Learn

 

Partner Conferences

Register Today for API World 2019 and Save $200!

The API World team has offered us 25 free OPEN Passes and discounted PRO Passes to API World 2019 so our members can attend the event.

 

API World (October 8–10, San Jose Convention Center) is the world’s largest API & Microservices conference and expo with 3,500+ attendees, 60+ exhibitors, and 10+ tracks covering API Lifecycle Management, API Innovations, Microservices, Containers, Kubernetes, and more. 140+ speakers include leaders from Intuit, US Bank, IBM, Okta, Capital One, Box, Kong, GitHub, Comcast, Microsoft, Postman, Twillio, SendGrid, Oracle, Ford, UPS, Uber, Google, eBay and 100+ more. 


GitLab Commit, our premier community event, brings together the GitLab community to connect, learn, and inspire. We want to make sure the NY tech community is well-represented at Commit so we are offering a HUGE discount to members of local tech community groups. You can use code 'COMMITCOMMUNITY102' to save 50%. 

 

Joshua D. Drake     September 04, 2019

What is Distributed SQL?

A distributed SQL database is similar to a NoSQL database in that it can globally distribute data and elastically scale. At the same time, it can also deliver strong consistency, ACID transactions and support the SQL syntax like you would expect from a monolithic SQL system.

Join us at Distributed SQL Summit at PostgresConf

YugaByte DB is excited to announce the speaker schedule for this year’s Distributed SQL Summit! Expert speakers will dive deep into the use cases, best practices and next steps for successfully implementing distributed SQL as a key part of an enterprise cloud and Oracle migration strategy.

Presented in partnership with PostgresConf, the inaugural Distributed SQL Summit is taking place on September 20, 2019 in San Jose, California. The Summit is the first ever event to focus exclusively on sharing best practices and technical knowledge on the cloud-native approach to deploying, operating and scaling distributed SQL databases. The Summit is co-located with Postgres Conference Silicon Valley, as a “conference within a conference.”

This one-day event features speakers and panelists from some of the biggest names in cloud and database infrastructure including Amazon Aurora, Google Spanner, Facebook,  Kroger and YugaByte DB. Here’s a small preview of some of the scheduled talks:

 

Keynote

James Watters, SVP Products – Pivotal

 

Panel: Facebook’s Distributed Database Evolution

Jeff Rothschild, Dhruba Borthakur, Vishal Kathuria, Karthik Ranganathan

 

An Introduction to Amazon Aurora

Kamal Gupta, Head of Engineering, Aurora – Amazon

 

Google Spanner’s SQL Evolution

Campbell Fraser, Software Development Lead – Google Spanner

 

Transforming the Omni-Channel Experience at Kroger

Mahesh Tyagarajan, VP Engineering – Kroger

 

Panel: How Cloud-Native and Distributed SQL are Transforming ECommerce & Retail

Moderator: Ram Ravichandran, CTO – Narvar

 

Distributed MySQL Architectures, Past, Present and Future

Peter Zaitsev, Founder & CEO – Percona

 

Building Microservices in a Cloud-Native World with Distributed SQL

Ryan Scheidter, Lead Software Engineer – Cerner

 

Make sure to check out the complete speaker schedule and secure your tickets for PostgresConf and Distributed SQL Summit!

Learn about YugaByte DB

YugaByte DB is an open-source, cloud-native, high-performance distributed SQL database for global, internet-scale apps. And best of all, it is fully compatible with the PostgreSQL wire protocol and the SQL syntax. Built using a unique combination of high-performance document store, auto sharding, per-shard distributed consensus replication and multi-shard ACID transactions (inspired by Google Spanner), YugaByte DB serves both scale-out RDBMS and internet-scale OLTP workloads with low query latency, extreme resilience against failures and global data distribution. As a cloud native database, it can be deployed across public and private clouds as well as in Kubernetes environments with ease.

Attend Talk on Thursday

Karthik Ranganathan, YugaByte’s Co-Founder & CTO, will be highlighting the challenges faced in building a PostgreSQL-compatible distributed SQL database in a talk titled “6 Technical Challenges Developing a Distributed SQL Database” (Thursday, September 19 at 12.30pm-12.50pm). This talk will serve as an excellent introduction to distributed SQL databases and prepare you to make the most of the Distributed SQL Summit the next day.

Visit Sponsor Table

Visit the YugaByte DB sponsor table at PostgresConf to learn how to build business-critical multi-cloud applications with maximum agility. You will see multiple demos with real-world use cases in action and have the opportunity to win some cool prizes.

See you at PostgresConf 2019 Silicon Valley

PostgresConf has always been an excellent resource for attendees to learn from their peers as well as Postgres experts. The 2019 Silicon Valley edition promises to the best ever. We look forward to connecting with you at the conference!

Jimmy Guerrero     September 03, 2019
Cybertec Logo Nameonly 01

 A database such as PostgreSQL is not just there to store data – it is also a tool to protect data. Your data must not be lost and it must not be seen by people who are unauthorized or hostile. The main goal is therefore to protect data at any cost and ensure that nothing is ever lost, leaked or compromised. As we have seen in the past more often than not a leak can easily ruin the reputation of a company or even lead to its destruction. This is true in all sectors including but not limited to finance, medical services, IT, and so on.

 

Protecting data at various levels

If you are using PostgreSQL you can protect data at various levels. The goal is to develop a comprehensive security concepts which protects from all kinds of attacks. The following aspects have to be taken into account:

  • Network security

  • Transport encryption (SSL, etc.)

  • Database level permissions

  • Data masking and obfuscation

  • Data-At-Rest Encryption (PostgreSQL TDE)

The following overview shows how to implement a sound policy at every level.

 

Ensuring network security

The first line of defense is always the network. The golden rule is: Only listen on network connections you really need and which offer a small attack surface. Fortunately, PostgreSQL has all the means to ensure security at this level.

The first thing to do is to configure the “listen_addresses” parameter in postgresql.conf. It tells PostgreSQL which bind addresses you want to use. The rule is: If you don’t have to listen on certain IPs don’t do it. To ensure security only use bind addresses which are really in use.

The second line of defense is pg_hba.conf. This config file will tell PostgreSQL how to authenticate which network segment. pg_hba.conf will be familiar to most readers so I will skip the details in this post.

However, let us assume that an attacker somehow manages to reach your database and launch a brute force attack to figure out your passwords. One way to defend against such an attack is to use the “auth_delay” extension which is part of the PostgreSQL contrib package. What is the general idea behind this extension? If an attacker launches a brute force attack auth_delay will wait some time before returning an error. This simple method will already greatly reduce your risk. Here is how it works:

# postgresql.conf

shared_preload_libraries = 'auth_delay'

auth_delay.milliseconds = '500'

Just add those lines to postgresql.conf and the module will take care of the rest.

 

Implementing transport encryption (SSL, etc.)

Once we have secured bind addresses and reduced the risk of a brute force attack it is important to protect your lines of communication. The way to do that is to use SSL. PostgreSQL supports various levels of SSL. The following levels are supported:

  • disable: I don't care about security, and I don't want to pay the overhead of encryption

  • allow: I don't care about security, but I will pay the overhead of encryption if the server insists on it.

  • prefer: I don't care about encryption, but I wish to pay the overhead of encryption if the server supports it.

  • require: I want my data to be encrypted, and I accept the overhead. I trust that the network will make sure I always connect to the server I want.

  • verify-ca: I want my data encrypted, and I accept the overhead. I want to be sure that I connect to a server that I trust.

  • verify-full: I want my data encrypted, and I accept the overhead. I want to be sure that I connect to a server I trust, and that it's the one I specify.

Depending on your performance and security requirements you can decide which level is best for you. Performance-wise SSL encryption does not come for free but if your security requirements are high it is worth paying the price.

 

Configuring database level permissions

Once you have taken care of network security, pg_hba.conf, authentication, as well as transport encryption it is time to take a look at what you can actually do inside the database.

The following layers of security are important:

  • schema: Make sure that only trusted people can access a schema

  • table: Ensure that only relevant people have access to a specific table

  • column: Restrict access to columns for specific users (to protect credit card data and alike)

  • row-level-security (RLS): Remove rows from the scope of a user

RLS (row-level-security) is especially important and promising because it allows people to only access specific rows in a table which greatly increases your ability to protect data in a very fain grained way. The important thing to keep in mind is: RLS is powerful but it requires proper testing. Some stuff is quite tricky and requires a fair amount of expertise as shown in my blog post about the topic (https://www.cybertec-postgresql.com/en/postgresql-row-level-security-views-and-a-lot-of-magic/). If you need assistance with RLS feel free to get in touch with us. We are pleased to help.

 

Data masking and obfuscation

Studies have shown that many attacks come from within. Consider the following scenario: You are running a large online shop. Your production database is secure and nothing happens. However, your development team has to test new stuff and needs data to ensure high quality standards. What are you going to do? Do you really want to give all your developers a full copy of all your data? The trouble is: If there is no proper test data your applications will be buggy – if you hand over all your data to developers you might face issues on the legal side of you are running the risk of giving data to people you cannot fully trust under all circumstances.

The solution to the problem is Cybertec Data Masking (https://www.cybertec-postgresql.com/en/products/data-masking-for-postgresql/). Our product will allow you to define an obfuscation model and give developers access to an obfuscated dump which can be used safely. The advantages are that the data given to developers has the same properties as the live data but does not contain personal or business critical data which should not be seen by ordinary developers.

Cybertec Data Masking provides some addons and extensions to PostgreSQL and helps you to obfuscate data in the most simple and elegant way possible. Get in touch with our sales team to find out more.

 

Enabling Data-At-Rest Encryption (PostgreSQL TDE)

Once you have secured your database using the steps outlined above you might still be faced with additional risks. What if your disks are compromised? PostgreSQL TDE (“Transparent Data Encryption”) will be the solution for you.

PostgreSQL TDE is a PostgreSQL distribution by Cybertec which automatically encrypts data on disk. All data files are safely encrypted and unless you know the key there is no way to launch your server. PostgreSQL TDE is especially useful if you are dealing with medical records, customer and financial data, which requires even more protection and security. PostgreSQL TDE is the ultimate solution to most high end security demands.

How does it work?

PostgreSQL will cypher every block as it is written to disk and decrypt data as it is read from your storage devices. Using cutting edge hardware acceleration TDE ensures superior performance and total transparency. PostgreSQL TDE can integrate into professional key stores and there is no need to store the key on the same server as the data.

 

If you are looking for PostrgreSQL TDE for PostgreSQL 11 or maybe even PostgreSQL 12 get in touch with our team here at Cybertec to find out more and to learn about this wonderful product:
https://www.cybertec-postgresql.com/en/products/postgresql-transparent-data-encryption/

(Author: Hans-Juergen Schoenig)

 

Hans-Jürgen Schönig     August 28, 2019

Timescale Sponsor Highlight Blog for PostgresConf Silicon Valley 2019

 As part of the countdown to PostgresConf Silicon Valley, learn more about featured Partner Sponsor Timescale, including their commitment to partnering with and contributing to the Postgres community.

 

Tell us about your commitment to the PostgreSQL Community.

As some background, TimescaleDB is built on top of PostgreSQL. By using PostgreSQL as a foundation, we’re able to give users scalable SQL for time-series data. 

We’re committed to increasing the usability of PostgreSQL and its compatibility with other products in the data ecosystem, which is why we’ve created software that helps others leverage the power of PostgreSQL. In addition to TimescaleDB, we’ve created many open source tools, such as pg_prometheus, a PostgreSQL extension for data from the popular monitoring system Prometheus; the prometheus-postgresql-adapter, which allows users to use PostgreSQL as a long term store for time-series metrics from Prometheus; the TimescaleDB/Postgres editor for Grafana, which is a visual query editor for the PostgreSQL datasource in the visualization tool Grafana; and a PostgreSQL output plugin for Telegraf, a machine monitoring tool.

Understanding how the community is using Postgres helps bring more awareness to the community's diversity and needs, which is why we recently created the State of Postgres survey. If you’re a Postgres user, please contribute to the community and take the survey!

 

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

We believe that the Postgres community is rapidly growing. Everyone’s eager to get involved, willing to listen and learn, and most importantly, willing to collaborate. 

We’ve seen countless examples in the Timescale Community Slack of users jumping in to help each other solve problems or to offer interesting points of view.

The community has also proved to be a great source of talent for Timescale, as we’ve hired many engineers who were PostgreSQL users and active community members. If you’re interested in working at Timescale, see our careers page!

 

Why is Postgres an ideal foundation to build a database?

Postgres was the ideal foundation for us to build TimescaleDB because it’s open source, SQL based, and has an active community. However, the main advantage was the fact that we could leverage its 30 years of reliability and stability that was already in existence. Additionally, Postgres has a robust ecosystem and many tools/extensions available.  For these reasons, Postgres allowed us to stand on the shoulders of giants, despite being a relatively young company.

 

Tell us why you believe people should attend PostgresConf Silicon Valley 2019 in San Jose.

PostgresConf SV is a great place to learn from people using Postgres in production! You get to meet members of the community face to face and form relationships that can lead to future collaboration. 

Timescale is also giving two great talks about our work with Postgres which we encourage you to come and check out: Advanced Compression in TimescaleDB with Hybrid Row/Culmnar Storage  (Thursday, September 19 from 4:20pm - 5:10pm) and Creating Continually Up to Date Materialized Aggregates  (Thursday, September 19 from 12pm - 12:50pm).

See you at PostgresConf Silicon Valley 2019!

Amanda Nystrom     August 27, 2019

 

It is late August, 2019. This is the time where we are usually prepping for the very busy fall season and not much else. However, this is the Year of Postgres and everyone is driving 200MPH down the ecosystem highway (321.8688/KPH). We are going to kick off this newsletter with some exciting information about the community.

Events

PostgresConf has launched Digital Events! The goal of Digital Events is to open our education platform year round to all members of the community. Our first series of events will be held with our ecosystem partner YugabyteDB and their “Distributed SQL Webinar Series.” This is a series of free-to-attend Webinars exploring Distributed SQL from leaders in the field.

 

PostgreConf Silicon Valley tickets are going at a brisk pace and half day trainings are almost sold out. Register today to reserve your seat before prices go up on September 1st!

 

Right after Silicon Valley, PostgresConf South Africa is kicking off. This conference has grown by leaps and bounds over the last two years. We highly recommend attending for anyone who can!

 

PGConf.IN (India) has announced that their conference will be held in February 2020!

Meetups

We have seen the launch of three new meetups this month:

  • Los Angeles Postgres The first meetup is planned for late October or early November as we continue to build the Silicon Beach community.
  • Toronto Postgres Similar to Los Angeles, the first meetup is planned for late October or early November.
  • Charm City Postgres This meetup was formed by long time community member Robert Treat.

 

Several other meetups are growing quickly: 

 

Interested in speaking or hosting a meetup? Contact us and we’ll connect you with the right people! 

Learn

Here is a short, great introduction tutorial on running PostgreSQL in Docker by Igal Sapir, Los Angeles Postgres organizer. Everybody has 13 minutes.

 

Shawn Wang from our friends at High Go has provided an insightful write-up on AES Performance.

Ecosystem

TimescaleDB is running a “State of Postgres” survey. Please take five minutes and help them out! They have also announced a new Distributed Timeseries product.

 

VMWare has just acquired Greenplum and PostgreSQL supporting company Pivotal.

Postgresql.org

PostgreSQL versions 11.5, 10.10, 9.6.15, 9.5.19, 9.4.24, and 12 Beta 3 are now out in the wild and addressing several important security concerns and bug fixes.

 

---

 

Have news you’d like included in future newsletters? Contact us.

Joshua D. Drake     August 23, 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

Brass tacks

  • Silicon Valley is selling tickets briskly, get yours today and join us at the largest gathering of Postgres leaders on the West Coast.

  • South Africa is set to release their schedule shortly. Watch the site for opportunities in October.

  • We have hinted at digital events in the past and they are in the final planning stages. Digital events will encompass best in class content from our community in the format of Webinars, Q&A sessions and Professional electronic training opportunities. Watch for more news on these unique opportunities as we get closer to Fall 2019.

Seasons

It is the middle of summer, and as Glenn Frey would say, “The Heat is on!” Summer is the time when everyone is busy, yet nobody is busy. You have a contract to execute but the signer is on vacation. You have a project to complete but your digital nomad developer took off for the beach. Suddenly even checks may be delayed because of a long weekend up in the mountains. It is also a time to catch up on the things that may have been overlooked. When the person driving your priorities is on vacation it is easier to step back and observe your purpose.

 

Introduction

At PostgresConf 2019 in Manhattan we organized a Diversity and Inclusion panel with the help of Plato. The panel was well attended, but not as much as we had hoped. This fact outlined that we had more work to do on expanding our leadership position within Diversity, Equity and Inclusion in the Professional Postgres community.

We take this topic very seriously and we would consider PostgresConf and our focus on People, Postgres, Data a success if the only outcome was for all to feel welcome and supported within our community. Thankfully we have organizers and volunteers who are passionate about this very topic.

We would like to introduce the PostgresConf and PgCentral Foundation DEI (Diversity, Equity and Inclusion) Work Group:

  • Debra Cerda: DEI Organizer

  • Henrietta Dombrovskaya: Contributor

  • Ryan Lambert: Contributor

  • Mara Lemagie: Contributor

  • Vikki McCormick: Contributor

  • Amanda Nystrom: Co-Chair Sponsor

Over the coming months we will be continuing to communicate our passion, our purpose, our action and our accomplishments in bringing true Diversity, Equity and Inclusion to our community.

“A genuine leader is not a searcher for consensus but a molder of consensus” -- Martin Luther King

 

PostgresConf Philly which is organized in conjunction with Philly Postgres sold out in July! A packed room, great content and glorious collaboration was available to all for free due to the generous support of the Wharton School for Business!

As we continue to build our professional relationships, connections with academia are going to be vital. Academia is one of the few spaces that Postgres has not been able to make assertive gains in adoption and it crucial to the long term vision of our community that Academia recognize and adopt Postgres as the World’s Database and a viable option for teaching the next generation of data experts.

 

International communication

As our community grows Internationally with strong ties to Asia, and countries in the Southern Hemisphere it becomes difficult to connect with those cultures using our normal nomenclature. In our last newsletter we used a quote meant to be a compliment and challenge to the Western communities to try new things. The quote was about pigs ears and how they are delicious. The quote was interpreted by some in the Asia community as negative.

While writing this newsletter, we had used a spelling variation for the term “Wowzers” which in American pop culture is meant to be an exclamation of amazement. However in other cultures it maintains a negative connotation causing us to change the term to Kapow. These communication challenges show us that we must be open and without pride in our communication. We must show patience and understanding with cultures that are not like ours and that the communities that are able to achieve this will lead the future of Open Source and Postgres.

“Every human is like all other humans, some other humans, and no other human” — Clyde Kluckhon

Joshua D. Drake     July 31, 2019

Latest Posts

  • Welcome to "Cultivating DEI" , a series in which Postgres community members share their insight and experience about creating a more diverse and inclusive Postgres environment where all are welco...
  • Come as you are The theme of Postgres Conference for 2020 is: Come as you are. We want everyone to feel welcome. You are welcome for your love of People, Postgres, Data and a desire to ascend be...
  • As part of the countdown to PostgresConf Silicon Valley, learn more about featured Partner Sponsor Pivotal, including their commitment to partnering with and contributing to the Postgres community....
  • Summer is officially over (although the calendar says otherwise), the kids are back in school, the last three-day camping weekend of the season has passed, and we are staring right at PostgresCon...
  • What is Distributed SQL? A distributed SQL database is similar to a NoSQL database in that it can globally distribute data and elastically scale. At the same time, it can also deliver strong consi...