Community Meetup Schedule Till the End of the Year

percona community meetups

percona community meetupsThis fall we started to run live-streamed online meetups accompanied by a live chat with the audience. Every week we invite experts for a real-time talk and devote this meeting to a specific database.

But the holiday season is coming soon! So, we slightly changed the meetup schedule and would like to announce it. Here are the dates of the upcoming events:

  1. November 17th – Meetup for PostgreSQL
  2. December 1st – Meetup for Percona Monitoring and Management (live stream from AWS re:Invent)
  3. December 8th – Meetup for MySQL
  4. December 15th – Meetup for PostgreSQL
  5. December 29th – Meetup for MongoDB

What do meetups look like? On Wednesday we gather in a virtual studio at 11 am EST/ 5 pm CEST and start streaming on YouTube and Twitch. Each event is dedicated to one open source database or technology. Experts share their knowledge with you and answer questions that you can ask on chat or on Discord. It is that simple, just come and join us!

Community Meetups Percona

Our next meetup will take place on November 17th. We will discuss autovacuum in PostgreSQL with Lead Senior Support Engineer Sergey Kuzmichev. Check out the event details on our Community website. You will learn more about autovacuum and get answers to your questions live. The Percona expert could even advise you on your particular issue during the live stream.

Normally guest speakers prepare some topics for discussion but things do not always go according to plan, and since it is a live stream, your question or suggestion to our amazing host Matt Yonkovit can change the direction of conversation dynamically.

The current meetup agenda for November 17th:

  • 1. Why do we need the autovacuum at all?
  • 2. How to stop worrying and start to love the autovacuum?
  • 3. Monitoring for related issues.

Percona MeetUp for PostgreSQL November 2021 - Autovacuum

Also, we have already run nine meetups and if you missed them, you can find their recordings here:

All the recordings, their transcripts, and also publications about future meetups are available on our Community website:

Come and talk about open source with us! If you feel inspired to participate in meetups not only as a listener but as a speaker, we would love to see you. Just contact us at to discuss your involvement.

Percona Open Source Community Meetups


Percona Is a Finalist for Best Use of Open Source Technologies in 2021!

Percona Finalist Open Source

Percona has been named a finalist in the Computing Technology Product Awards for Best Use of Open Source Technologies. If you’re a customer, partner, or just a fan of Percona and what we stand for, we’d love your vote.

With Great Power…

You know the phrase. We’re leaving it to you and your peers in the tech world to push us to the top.

Computing’s Technology Product Awards are open to a public vote until October 29. Vote Here!

percona Best Use of Open Source Technologies

Thank you for supporting excellence in the open source database industry. We look forward to the awards ceremony on Friday, November 26, 2021.

Why We’re an Open Source Finalist

A contributing factor to our success has been Percona Monitoring and Management (PMM), an open source database monitoring solution. It helps you reduce complexity, optimize performance, and improve the security of your business-critical MySQL, MongoDB, PostgreSQL, and MariaDB database environments, no matter where they are located or deployed. It’s impressing customers, and even competitors, in the industry.

If you want to see how Percona became a finalist, learn more about Percona Monitoring and Management, and be sure to follow @Percona on all platforms.

Vote Today!


Reminder: TokuDB Storage Engine Will Be Disabled by Default in Percona Server for MySQL 8.0.26

TokuDB Disabled in Percona Server for MySQL

TokuDB Disabled in Percona Server for MySQLAs we’ve communicated in our blog post in May, the TokuDB Storage Engine has been marked as “deprecated” in Percona Server for MySQL 8.0. It will be removed in a future version (Percona Server for MySQL 8.0.28, expected to ship in Q1 2022).

With the release of Percona Server for MySQL 8.0.26, the storage engine will still be included in the binary builds and packages but will be disabled by default. If you are upgrading from a previous version, the TokuDB Storage Engine plugin will fail with an error message at server startup if it is installed.

You will still be able to re-enable it manually so that you can perform the necessary migration steps.

Re-enabling the TokuDB Engine in Percona Server for MySQL 8.0.26 is fairly straightforward. You need to add the options




options to your my.cnf file and restart your server instance.

Once the server is up and running again, you can migrate your data to an alternative storage engine like RocksDB or InnoDB before disabling and removing TokuDB. See the chapter Removing the TokuDB storage engine in our documentation for details.

Let us know if you have any questions or comments about this process!

If you need any assistance with migrating your data or have any questions or concerns about this, don’t hesitate to reach out to us – our experts are here to help!

Complete the 2021 Percona Open Source Data Management Software Survey

Have Your Say!


Lessons From Peter Zaitsev…

Tom Basil Peter Zaitsev Percona

Tom Basil Peter Zaitsev PerconaPeter Zaitsev, known to all as Percona’s founder and CEO, asked me to pen a few reminisces as I retire.  How do I sum up 22 years in the MySQL world?  How do I even begin?  I best start with gratitude. I’ve had the amazing privilege of being on the inside of the leadership teams of two highly impactful software startups, MySQL and Percona.

I now find myself as Percona’s first-ever retiree.  So I write as PZ requested of me, with the caveat that these reflections are wholly my own.  They do not necessarily reflect Percona policy or even Percona’s current conditions, as I’ve been less in the front lines in recent times.

Tom, Monty Widenius (MySQL Founder), Heikki Turri (InnoDB Creator), & Peter, at the 2nd ever MySQL User Conference, 2004

Tom, Monty Widenius (MySQL Founder), Heikki Turri (InnoDB Creator), & Peter, at the 2nd ever MySQL User Conference, 2004

I became a MySQL DBA in late 1999.  My then-boss in Maryland agreed to buy the highest tier support offered by the fledgling MySQL company in Finland.  A $12,000 annual payment got you the personal telephone numbers of everyone in the company, then maybe a half dozen persons, and quick answers to your emails often direct from company founder Monty Widenius.  The passionate intensity of MySQL support was unlike anything I’d ever experienced.  I loved it, while the speed and simplicity of MySQL delighted me.

Monty Widenius and co-founder David Axmark pioneered the now-familiar pattern of open source software employment – no in-person job interviews, work at home from anywhere via the internet, then fly all over the world for meetings and conferences.  But when Monty invited me to join MySQL Ab in 2001, this was still pretty weird stuff, at least in the USA.  My wife was incredulous that I’d take a job from some guy in Finland whom I’d never met and who gave away his software for free.  As I once wrote in 2007:

I had a much better Oracle DBA offer from a large bank, and six kids (ages 2 to 13) plus my wife at home.  To her the bank was a sure bet and a virtual boss in Finland an absurd risk.  But MySQL struck me as an exciting company that kept its promises.  What to do?  I asked a trusted (Catholic) priest for his opinion.  He surprised me and voted for MySQL.  I borrowed a bedroom from the kids as my office and joined MySQL as employee #11.

Monty, Vadim, & Peter share dinner, 2008

Monty, Vadim, & Peter Share Dinner, 2008

Monty appointed me Director of Support.  This ultimately grew to be a team of 60 high-end experts.  This was another of Monty’s innovations – technical support was not an entry-level role but a senior-level one, a prestigious career destination for top experts.

Twenty years seems not that long ago.  Yet so much that’s considered ordinary now wasn’t then.  Neighbors assumed I was really unemployed until I started to travel to Europe pretty regularly.  Everything inside MySQL was transacted by email.  No Zoom, no Slack, no Confluence, nor any other of today’s common tools were then known.  Maybe within a year of my joining MySQL, we began using Internet Relay Chat, or IRC.  Having real-time chat among a global team was breakthrough technology.  Yet, the IRC command line was too geeky for admin staff, so it never became a company-wide tool.

Another novelty though now commonplace, was a 100% global workforce.  I had been in my mid-30s when the Cold War ended in 1991.  Throughout my formative years, Russians, Ukrainians, Estonians, Bulgarians, and Serbs lived trapped behind the Iron Curtain, far distant from ordinary Americans like me.  Now they had become my daily co-workers and personal friends.  For me, it was another bit of cultural whiplash of the MySQL era.

MySQL experts were then extremely scarce.   In 2002 Monty called me excitedly.  A Russian MySQL prodigy had just accepted his job offer.  His name was Peter Zaitsev, and Monty wanted me to be his manager.  That year the entire MySQL company fit into one bus and rode from Helsinki to St. Petersburg to meet our new Russian colleagues.  Peter looked to me like a teenager.  In reality, he was age 20, married with one child, had a Master’s Degree in Computer Science, and was already a serial entrepreneur. He’d built his Russian startup Spylog around InnoDB, making himself one of the world’s first experts on this now ubiquitous storage engine.

Peter & Monty at the MySQL User Conference, 2008

Peter & Monty at the MySQL User Conference, 2008

I created the “High-Performance Group” within MySQL Support as a home for Peter to run.  He was in demand all over the globe to troubleshoot difficult MySQL cases.  He badly needed a deputy, and this is how Vadim Tkachenko entered my life.  It also became the first of many business lessons I would learn from Peter.  Peter is young enough to be my son.  But regarding entrepreneurship, it has been the reverse, Peter the father teaching me the son.

One lesson personified in Vadim was how demanding Peter was in his hiring standards.  He disqualified many applicants who struck me as very well qualified.  Peter painstakingly probed and tested Vadim’s coding expertise.  But the fruit of that care has shown in their long partnership and the technical excellence that Percona is known for.  More troubling is that when I approved Vadim’s hiring, I had no warning of his wry sense of humor or that I would ever become its victim.  How often I have paid for this oversight in the ensuing years.

In 2006 Peter and Vadim left MySQL to launch Percona and invited me to join them.  MySQL had by now become well established, with 400+ staff and strong VC backing.  Peter had only Vadim and a good reputation, but no money.  Peter argued loudly with me – he is known for this – that Percona would become the future of MySQL.  Peter said trends were shifting in his favor, and if I had any sense, I’d see it and get onboard.

I was then comfortable and established in MySQL Ab.  I saw no need at age 53 to risk everything (again) on a two-person startup.  But in 2008, Sun acquired MySQL for $1 billion. Sun’s culture was big corporate America and so unlike the freewheeling Scandinavian culture of MySQL.  And being the CEO’s friend at a tiny startup seemed a better place to live than the anonymous middle tiers of a downsizing megafirm.

So I quit Sun and became Percona’s first COO, a title I held for seven years.  Later, Peter named me Percona’s Chief of Staff, a role I held until my retirement.  In total, I was Peter’s boss for four years, and then he was my boss for 13 years.  Vadim went from my second-level report to being my second boss. The arrangements of fate are indeed curious.

So what have I witnessed at Percona, and what have I learned from it all?  

Foremost is that in a certain sense, Percona is a web of friendship. It’s a nexus of skilled people who cooperate, communicate, help, and labor hard as friends around a common endeavor.  Seeing Percona as a family is an exaggeration, but seeing it as a community of highly interdependent friends is not.  The enjoyment of friendships I’ve seen among staff, especially at conferences and meetings, has been deep and real.

Tom jumps off a cliff with Percona colleagues in Cancun, 2011

Tom jumps off a cliff with Percona colleagues in Cancun, 2011

My memories of Percona include events in California, Texas, New York, North Carolina, Quebec, Mexico, the Dominican Republic, Ireland, the United Kingdom, the Netherlands, Portugal, Switzerland, Estonia, Ukraine, Croatia, and Montenegro.  These remain precious memories, and I’m certain I’m not alone in this.  The relationships nurtured in these events build up reservoirs of trust and goodwill.  This is what oils the progress made during the long months of working in isolation from home.

Percona also welcomed families to most Percona events.  My wife and I shared seven trips with Percona to attractive locales.  She made Percona friends of her own with whom she’d enjoy reunions.  Kids came too, a few times.  We also hosted Percona guests in our home.

Vadim with Tom & his wife Kathleen at their home in Maryland, 2007.

Vadim with Tom & his wife Kathleen at their home in Maryland, 2007.

Consciously making Percona a family affair was another of Peter’s ideas and a very good one for business.  That my family’s welfare was directly tied to Percona’s success was understood by each of us.  When I had to upend our schedule for the Percona crisis du jour, family complaints were few.  My wife and children’s connectedness with Percona also made working remotely less isolating for me.

I think the interruption of professional friendships has been the worst consequence of the Covid pandemic for Percona.  Friendships can be built online too, but it’s much harder when done among those who’ve never once met. There’s something about relating in person that’s unique.  The virtual world can imitate but not replace it.

When friends are dealing with friends, all problems get resolved without managerial escalation or bureaucratic morass.  All sorts of improvements get implemented with minimal friction.  Peter usually fosters debate and invites dissenting opinions, as did Monty and MySQL CEO Marten Mickos before him.  Yet honest debate and credible decisions require trust.  And trust is best fostered within an atmosphere of authentic friendships.

This dynamic was at play inside MySQL Ab, and I think a big factor in powering MySQL to prominence.  Percona, at its best, has continued with this and many other MySQL traditions.  For instance, Percona’s monthly All Company Zoom calls are where the entire staff is trusted with batches of corporate metrics, both good and bad, and staff can directly question the CEO.

Yet friendship is not indulgence.  Another PZ business lesson I’ve imbibed is that deserved firing is an act of friendship towards the company as a whole.  I didn’t fully grasp this pre-Percona.  Not everyone makes a worthy friend, and some need to depart before they drag down the whole.  Friendship is also not indiscreet.  Transparency has proper limits, and some things cannot be explained or even acknowledged.

Another PZ lesson is that what (or who) got you here isn’t what will get you where you need to go.  At a certain point, Percona outgrew me as COO.  I had the work ethic but not the skills or experience for Percona’s larger corporate stage.  Peter helpfully explained this to me at one of our less agreeable meetings.  Needful directness is another of his business attributes.

A few years ago, a high-priced consultant flattered our Executive Team by explaining that only 0.4% of all startups reach Percona’s age and size.  That means 99.6% of startups don’t survive at all or end up far smaller than Percona if they endure.

The absolute necessity of constant adaptation to a swirl of change became another lesson.  I saw in Peter a constant lookout for what’s the next opportunity, the next danger, the process to strengthen, etcetera.  My temperament favors stability and predictability, but I learned its limits in a competitive marketplace.

Seizing an unexpected opportunity was part of this lesson. It’s the lesson of taking action now when an opportunity appears, not when it’s convenient. It’s hard to believe, but Percona software wasn’t, at first, part of any grand master plan.  Percona did consulting, period.  But MySQL Ab had let InnoDB development languish for tangled reasons.  Desperate for a workaround, some experts inside MySQL privately asked us to release all of the InnoDB performance patches Percona had accumulated.

These patches were at first bundled as XtraDB, a drop-in replacement for the InnoDB engine.  Later this grew into the Percona Server for MySQL, a drop-in replacement for MySQL.  Ultimately it grew into a full-fledged engineering team with Percona versions of MySQL, MongoDB, and PostgreSQL, plus the Percona Monitoring and Management (PMM) dashboard.  But in a certain sense, Percona’s entire future sprung from seizing one unexpected and seemingly small opportunity.

Peter awards Tom a Percona University PhD!

Peter awards Tom a Percona University Ph.D.!

What does the CEO’s life consist of?  What I witnessed includes –  Endless meetings.  Upset customers.  Aggressive competitors.  Flaming disagreements.  Sudden resignations.  Regulatory swamps.  No money for payroll.  Paying others but not yourself.  Failing products.  Whispering critics.  Continual interruptions.

Crisis after crisis gets lobbed at the CEO, often several at once.   It takes guts just to persevere and to improvise when no visible solution exists.  I recall an early Executive Team meeting that Peter ran for sixteen straight hours trying to deal with everything; then he reconvened us for more of the same after a few hours of sleep.

I hope Peter and Vadim get rich.  Guts should have its reward.  I might not have thought this pre-Percona.  But life in its trenches convinced me.  Expert tech opinion bet heavily against Percona early on.  Voices said there’s no profit in consulting, you’re too niche to survive, VC money is your only hope, and similar refrains.  It takes some guts to stand alone and not cave into the doubters, especially when there’s a faction on your own leadership team chanting “give up now.” Simply surviving is underappreciated for the victory it represents.

How do you explain business risk to those who’ve never lived it?  What does it feel like to have hundreds of families depend on your payroll?  How do you cope knowing that other people pay hard for your own mistakes?  Percona once misjudged and had to quickly lay off 20 people.  It was painful not only for them, since Peter as CEO bore conspicuous responsibility.

I, too, dreamed of VC money as easier than the painful austerity of a bootstrap.  Peter was a fanatic about keeping Percona independent.  Only gradually did I see how Percona’s freedom from VC interference was paying off.  A near-term VC exit strategy looks very different from a lifetime venture strategy.  Perhaps VC oversight would have given Percona more discipline and consistency inside or had other benefits.  But I doubt it would have been worth it.

My career ended as it began.  My boss told me he’d hired a Russian prodigy and asked me to become his manager.  The boss this time was Peter, and the employee was Daniil Bazhenov.  Daniil barely spoke English, but Peter assured me he was a quick learner and that we’d find a way.  We did, along with some amusement.  In another bit of cultural whiplash, Daniil’s worked for me from Ulyanovsk, Lenin’s hometown.

Tom & Daniil on the beach in Punta Cana, 2020

Tom & Daniil on the beach in Punta Cana, 2020

I could ramble on and on.  But I close my blog and professional life with images of so many wonderful people, which flood my mind.

I think of Monty, who opened the door for my MySQL future, and of my wife Kathleen, who trusted me to walk through it.  I think of those very first MySQL employees, Sinisa Milivojevic, Jani Tolonen, Tim Smith, Matt Wagner, Jeremey Cole, and Indrek Siitan, who first wooed me with MySQL’s beauty and excellence.

I think of the MySQL Support Team leaders to whom I owe so much:  Dean Ellis, Salle Kermidarski, Lachlan Mulcahay, Bryan Alsdorf, and Miguel Solorzano.  Joined with them are Mark Leith, Tonci Grgin, Hartmut Holtzgraffe, Victoria Reznichenko, Todd Farmer, Geert Vanderkelen, Domas Mituzas, Harrison Fisk, Hartmut Holzgraefe, Kolbe Kegel, Matt Lord, Shawn Green, Ligaya Isler-Turmelle, and many others to whom I owe a great debt, including Ulf Sandberg, my boss.

Finally, from my MySQL years, I think of David Axmark, Marten Mickos, Kaj Arno, Zack Urlocker, Edwin Desouza, Brian Aker, Boel Larsen, and other key players who, with Monty, navigated MySQL to stunning success. Please forgive me if the fading of time means I’ve omitted a name I should never forget.

And of my Percona years, how can I begin to name with gratitude everyone I ought with whom my Percona life has intersected.  I can only say thank you and again ask forgiveness for any omissions.

First, I think of those who were part of my teams over the years or whom I helped recruit:  Mark Sexton, RIP.  Svetlana Prozhogin.  Kortney Runyan.  Natalie Kesler.  Andrey Maksimov.  Agustin Gallego.  Colin Charles.  Drew Sieman.  Lorraine Pocklington.  Daniil Bazhenov.  Laura Byrnes.  Aleksandra Abramova.  Fredel Mamindra.  Jana Carmack.

I think of those Percona experts with whom I had the chance to closely interact at different times:  Michal Coburn. George Lorch.  Alexander Rubin.  Ovais Tariq.  Marcos Albe.  Alkin Tezuysal.  Marco Tusa.  Liz van Dijk.  Kenny Gryp.  Dimitry Vanoverbeke.  Przemek Malkowski.  Lenz Grimmer.  Ibrar Ahmed.  Tate McDaniel.  Yves Trudeau.  Yura Surokin.  Mykola Marhazan.

I think of those EMT colleagues with whom I shared so many long meetings:  Baron Schwartz.  Bill Schuler.  Ann Schlemmer.  John Breitenfeld.  Matt Yonkovit.  Sam Duffort.  Bennie Grant.  Jim Doherty.  Plus Keith Moulsdale of Whiteford, Taylor, Preston, Percona’s expert legal counsel for many years.

I think of those who’ve moved on but remained friends of Percona:  Peter Farkas.  Ignacio Nin.  Bill Karwin.  Aurimas Mikalauskas.  Sasha Pachev.  Raghu Prabhu.  Peter Schwaller.  Roel van de Paar.  Evgeniy Stepchenko.  Morgan Tocker.  Brian Walters.  Ewen Fortune.  Ryan Lowe.

Tom thanks Vadim for his gift of retirement guidance!

Tom thanks Vadim for his gift of retirement guidance!

And Vadim Tkachenko, how could I almost forget you?!

And Peter Zaitsev.  I am so glad we met.


Congratulating Marcelo Altmann on his Promotion to Oracle ACE!

Marcelo Altmann promotion to Oracle ACE

Marcelo Altmann promotion to Oracle ACEWe’re excited to share that Marcelo Altmann from the Percona Server Engineering Team has just been promoted from Oracle ACE Associate to Oracle ACE.


The Oracle ACE Program recognizes and rewards community members for their technical contributions to the Oracle community.

Marcelo initially joined Percona as a senior support engineer in our global services organization, where he helped customers with running their MySQL-based environments. In early 2020, he joined our Server Engineering team and has been actively involved in the development of Percona Server for MySQL and Percona XtraBackup since then.

Marcelo’s contributions to the MySQL ecosystem are countless – he’s an active blogger, he regularly submits bug reports to the MySQL team, organizes local and virtual meetups, and also contributes patches and bug fixes.

Congratulations again, Marcelo, we’re proud to have you on our team!


Percona Server for MongoDB 5.0.2 Release Candidate Is Now Available

Percona Server for MongoDB 5.0.2

Percona Server for MongoDB 5.0.2We’re happy to announce the first release candidate of Percona Server for MongoDB version 5.0.2 (PSMDB). It is now available for download from the Percona website and via the Percona Software Repositories.

Percona Server for MongoDB 5.0.2 is an enhanced, source-available, and highly scalable document-oriented database that is a fully compatible drop-in replacement for MongoDB 5.0.2 Community Edition. It includes all the features of MongoDB 5.0.2 Community Edition, as well as some additional enterprise-grade features.

The most notable features in version 5.0 include the following:

  • Resharding allows you to select a new shard key for a collection and then works in the background to correct any data distribution problems caused by bad shard keys and improve performance.
  • Time Series Collections are aimed at storing sequences of measurements over a period of time. These specialized collections will store data in a highly optimized way that will improve query efficiency, allow data analysis in real-time, and optimize disk usage.
  • Resumable Index Builds means that the index build for a collection continues if a primary node in a replica set is switched to another server or when a server restarts. The build process is saved to disk and resumes from the saved position. This allows DBAs to perform maintenance and not worry about losing the index build in the process.
  • Window operators allow operations on a specified span of documents known as a window. $setWindowFields is a new pipeline stage to operate with these documents.
  • Versioned API allows specifying which API version your application communicating with MongoDB runs against. Versioned API detaches the application’s lifecycle from that of the database. As a result, you modify the application only to introduce new features instead of having to maintain compatibility with the new version of MongoDB.

Additionally, new aggregation operators such as $count, $dateAdd, $dateDiff, $dateSubtract, $sampleRate and $rand are available with this release.

Note: As with every major release, version 5.0 comes with a significant number of new features and is still being rapidly updated. At this point, we’re making this version available as a “Release Candidate” only and we strongly suggest not to use it for production environments yet. However, we do encourage the use of this version in test and development environments.

We’re also still in the process of integrating support for version 5.0 into our other products. While Percona Backup for MongoDB 1.6.0 has just been released to support this version, some other products still need to be updated and tested.

For example, the Percona Distribution for MongoDB Operator will have PSMDB 5.0 support from version 1.10.0, which is slated to happen in mid-September.

On the Percona Monitoring and Management side, Percona Server for MongoDB 5.0 support is scheduled to be included in version 2.22.0 (currently targeting the end of September).

Because of these factors, we will not release version 5.0 of our Percona Distribution for MongoDB until we’ve updated these products and have gathered enough confidence to remove the “release candidate” label.


Platform End of Support Announcement for Ubuntu 16.04 LTS

EOL Ubuntu 16.04

EOL Ubuntu 16.04The End Of Support date for Ubuntu 16.04 LTS is coming soon. According to the Ubuntu Release Life Cycle, it will be at the end of April 2021. With this announcement comes some implications to support for Percona software running on these operating systems.

So we will no longer be producing new packages and binary builds for Ubuntu 16.04.

We generally align our platform end of life/support dates with those of the upstream platform vendor. The platform end of life/support dates are published in advance on our website on the  Percona Software support life cycle page

According to our policies, Percona will continue to provide operational support for your databases on Ubuntu 16.04. However, we will be unable to provide any bug fixes, builds, or OS-level assistance if you encounter an issue outside the database itself.

Each platform vendor has a supported migration or upgrade path to their next major release. Please reach out to us if you need assistance in migrating your database to your vendor’s supported platform – Percona will be happy to assist you.


CVE-2020-29488: Changes in How Absolute Paths are Handled in Percona XtraBackup xbstream


CVE-2020-29488Due to CVE-2020-29488, Percona XtraBackup is modifying how xbstream handles absolute paths to prevent malicious file injections. Like the tar archiving utility, the new behavior removes the leading ‘/’ character and references to the parent directory.

Fixes are available in Percona XtraBackup versions:

>= 2.4.22

>= 8.0.23-16.0

For example, ../../../d1/../d2/h.txt will be saved in the stream with the relative path ./d2/h.txt.

The updated function provides a warning when creating a stream with a file with an absolute path:

$ xbstream -c /tmp/data

xbstream: Removing leading '/' from member names

The function also will not extract files with absolute paths:

$ cat a.xb | xbstream -x -C  ./restore

xbstream: absolute path not allowed: /tmp/bar.txt

Note: a stream can contain an absolute path if created with an older version of xbstream or if the following parameter is used:

  • -P, --absolute-names

Be aware of the following:

Scripts that call xbstream to store the path/file in an absolute path will strip the leading ‘/’ and references to ‘../’. This action could cause an unexpected result.

Extracting older formatted binaries which do contain the leading ‘/’  and path/file produce an error message and are not extracted.


Hoss Talks Foss: The Podcast is Now Available

Percona Open Source Podcast

Percona Open Source PodcastGreat news!  Percona’s Community-focused podcast, hosted by none other than the HOSS (Head of Open Source Software) himself (yeah, that is me), is now available on almost all podcast platforms.

What? You didn’t know we had a podcast?

We do, and we’ve had some great episodes since we started in January. In fact, we just published our 10th episode! We talk about all things open source-related on the podcast, from SSPL, MySQL, PostgreSQL, MongoDB, MariaDB, Linux, and more!  We will also be touching on a ton of other tech topics as well. Here’s a quick recap in case you missed any episodes.

Currently Available Interviews and Discussions:

In episode #1, we sat down with Peter Zaitsev (Percona’s CEO) to talk about open source, the cloud’s impact, and investors on open source licensing.  We also cover the news about Elastic adopting the SSPL license.  

[Video Link: SSPL and the Cloud]

In episode #2 we sat down with Walter Garcia (Remote Database Engineer) to talk about MySQL backups.  We talk about not only best practices but also touch on the biggest mistakes when setting up backups. 

[Video Link: MySQL Backups]

Episode #3 is all about running your database in K8 (Kubernetes).  In this episode, we sit down with Sergey Pronin to talk about the evolution of Kubernetes and why people are looking at it for databases.   

[Video Link: Databases on Kubernetes]

Have open source expertise you want to share? Submit your talk for Percona Live ONLINE 2021!

Episode #4 We catch Up with Pingcap/TiDB developer Morgan Tocker and talk about contributing to OSS and TiDB.  Morgan has been in the MySQL community for longer than I have, and we chat about old projects, swap fun stories, and talk about contributing.  

[Video Link: TiDB, Open Source, and MySQL]

David Murphy joins us on episode #5 to catch up on all things DevOps, SRE, and DBRE related.  David has been a long-time contributor in the MongoDB, MySQL, and open source communities.  He talks about how the DBA role is evolving and how he helps to modernize the infrastructure at a major international airline (including mixing  Oracle, MongoDB, MySQL, and PostgreSQL).  

[Video Link: SRE, DBaaS, and DevOps for Databases]  

Open Source Podcast

In episode 6, we catch up with Google Dev Advocate Gabi Ferrara.  Gabi and I discuss her career in the database space and how she progressed and had to work to reach the point where she is today. Gabi free offers her advice to others trying to break into the tech industry.  We also talk about the database and development challenges and struggles she helps people overcome in her current role.   

[Video Link: Google Cloud, Dev Rel, and SQL

In episode 7, we catch up with long-time engineer and community member Lenz Grimmer.  Lenz is currently our Sr Director of Server Engineering at Percona.  He talks about open source communities, how to contribute, and where we have come from.  

[Video Link: Database, Open Source Contributions, Engineering, and Linux

We celebrate episode 8 by bringing in Datastax VP of Engineering EMEA Henrik Ingo.  Henrik talks about his time at MySQL, MariaDB, and MongoDB before Datastax (he has seen the inside of many great database companies).  Henrik talks about Datastax and how his team is opening up more to the open source community while other companies are locking more down.  It is a fascinating discussion and one not to be missed.  

[Video Link: DataStax, MongoDB, FOSS, and Openness

In episode 9, we explore ARM-based EC2 instances with Jobin Augustine.  The new instances are cheaper, faster, and better for the environment!  We talk through benchmarking the new instances and the benefits.   

[Video Link:  Graviton2 ARM Performance, Benchmarks, and PostgreSQL]

Finally, in the 10th episode, we talk to Alkin Tezuysal about all things Vitess and MySQL.  Alkin works for Planetscale and is one of the maintainers for Vitess.  We talk about use cases, how to contribute, and who is using Vitess in the wild.

[Video Link:  Talking Vitess, Scaling Databases, and Sailing]

The Hoss Also Had a Couple of HOSS Quick Hits (Not Exactly Full-Length Podcasts, but Interesting Quick-Hit Topics)

How about 7 minutes on MongoDB Performance Tuning?   I sat down with Mike Grayson and asked him the most important things to tune in MySQL after upgrading the memory.  

[Video Link: Tuning MongoDB’s Memory after an upgrade]

Want the short version of the difference between MongoDB replication and sharding and when to use each?  In this 12-minute video, Akira Kurogane sits down with the HOSS to explain how replication and sharding work in MongoDB.   

[Video Link:  MongoDB Sharding 101]

Percona CommunityFuture Topics – Community Driven

Have an idea for a future show?  Want to be a guest?  Drop me a line at!



database podcastWhere Can You Find the Podcast?

You can watch the video versions (if you can handle 30-40 minutes of me staring awkwardly at the camera) on YouTube. You can also subscribe on popular platforms like Podbean, Google, and Apple.

Note: YouTube has all the episodes today in this playlist, and other podcast services will fill in the episodes over the next week.

Have a great day, everyone!


2020 Percona Survey Results Reveal the Latest Open Source Database Trends

Percona 2020 Open Source Survey

Percona 2020 Open Source SurveyAt our recent Percona Live ONLINE we announced the release of the 2020 Open Source Data Management Software Survey results. 

This year, we wanted to build upon the data we collected in 2019 and continue to monitor the open source industry’s pulse. The 2020 survey was perhaps reflective of the wider world environment, as companies indicated a desire to consolidate their database infrastructure and software, avoid risk, and manage costs.

We asked a number of new questions, as well as comparing 2019 data. One of the headline findings is that database footprints and Database as a Service (DBaaS) continues to grow, but that many companies are facing unexpected cloud bills.

According to the results, the cost of cloud computing was flagged as a problem for many companies, with 22% of organizations facing additional unplanned costs from their cloud providers.

The share of companies using DBaaS increased to 45% of respondents compared to 40% the previous year. More than half of large companies (56%) indicated that they use DBaaS, and, in-line with the trend of companies looking to mitigate their risk, around half of the total large company category used more than one DBaaS service.

The survey also revealed a number of other interesting data points:

Decisions on open source database choice are centralizing

open source survey

  • Architects are now the primary group in charge of making database deployment decisions, according to 41% of respondents.
  • The next group is developers with 26%. So, although many developers remain responsible for their organizations’ technology choices, this is starting to consolidate based on the need to manage support and management overheads.



Database footprints continue to grow

Database footprints continue to grow

  • 82% of organizations saw their database footprint grow more than 5% per year.
  • For 12% of organizations, the volume of data they held doubled or more in twelve months.




Upgrading cloud instances is a common occurrence

Upgrading cloud instances

  • Around 28% required two to three upgrades, while 21% had more than ten upgrades.
  • Just 12% of organizations made no changes to their instances.




Cloud spending and planning gave mixed results

Cloud spending

  • Around 22% found that their cloud spending was above expected, while 60% found their cloud spending was about right. For 17%, their cloud spend was lower than expected.




What keeps you up at night?

  • This year, we dug deeper into the issues that companies face in their environments and their biggest database management concerns. When asking, ‘what keeps you up at night?’ the most significant issues flagged were downtime (59%) and performance (51%), along with the concern of fixing emergency issues (35%).
  • Performance issues were by far the biggest experienced issue for nearly three-quarters of respondents at 74%, with unplanned downtime impacting 45%.

Given the negative impact that performance issues and downtime has on businesses, this reiterates how crucial it is to ensure that your databases are correctly configured and optimized.

Huge thanks to everyone who gave their input and helped contribute to the success of this project. 

Visit our website to view the full 2020 results and see a comparison with 2019 figures.

Powered by WordPress | Theme: Aeros 2.0 by