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.

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)

There were 20 attendees, including Melanie Plageman of Pivotal presenting/coordinating “Postgres Patch Review,” and Postgresql.org -Hacker Jeff Davis as hands on help. This was the first workshop of its kind for Silicon Valley Postgres and with the feedback received, we are planning to plan similar events at least twice a year to provide an opportunity that is currently not available elsewhere. (Sneak peek: there may be one at PostgresConf Silicon Valley on October 15th and 16th, which is right around the corner!)

Eight patches were reviewed, with three including specific feedback to the patch authors:

• Bhushan Uparkar on Index Skip Scan
• Mathias Brossard on psql command to show size of partition table
• Kaiting Chen on fixing quadratic performance of regexp match/split functions

We’re excited to be a part of this path of Postgres contributor building. Hopefully it will be a model for other meetups and community partners to follow in continuing to contribute to the Most Advanced Open Source Database ecosystem.

Silicon Valley Postgres is the fastest growing Postgres user group within North America. It was initiated just 12 months ago and will reach 700 members likely before Monday. The group exists to help all facets of Postgres users and the Postgres ecosystem, including, but not limited to, PostgreSQL, Greenplum, Aurora Postgres, AgensGraph, Yugabyte, ZomboDB, TimescaleDB.

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.

March 18th and 19th will have immersive training. Instructors are encouraged to submit half and full day material for consideration. The preferred topics are centered around Postgres but anything People, Postgres, or Data related will be considered.

Monday, March 18th through Friday, March 22nd will host several partner summits, including popular and upcoming topics within the Postgres community and the annually hosted Regulated Industry Summit. Break out sessions will be held from Wednesday - Friday.

In addition to the partner summits, PostgresConf 2019 will offer multiple program tracks with Postgres related topics including (but not limited to): 

• Postgres Internals
• Postgres Administration
• Operations and Development
• Data
• Cloud
• Database Security and Compliance
• Use Cases
• Regulated Industries
• Telecommunications
• Healthcare and life sciences
• Railroad, airline and pipeline transportation
• Oil and gas
• Electric power and transmission
• Financial services and trading 

PostgresConf is a global nonprofit conference series with a focus on growing community through increased awareness and education of Postgres and related technologies. PostgresConf is known for its highly attended national conference with the mission of:

PostgresConf Silicon Valley is being held October 15th-16th at the Hilton San Jose and the schedule is now available.

• Using TimescaleDB for time-series storage and analytics in Postgres
• Designing applications on top of a distributed PostgreSQL

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.

Community,

• Amazon
• Pivotal
• 2ndQuadrant
• Microsoft
• Timescale
• HighGo
• Data Dog
• Fivetran
• BlueTalon
• Goldman Sachs
• forhims
• Immuta