# Open source, PostgreSQL, and risk mitigation in an era of … | Percona Community

**URL:** <https://forums.percona.com/t/open-source-postgresql-and-risk-mitigation-in-an-era-of-percona-community/40019>\
**Category:** Community website\
**Created:** [January 9, 2026, 2:02pm UTC](https://forums.percona.com/t/open-source-postgresql-and-risk-mitigation-in-an-era-of-percona-community/40019 "2026-01-09T14:02:49Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![daniil.bazhenov](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/daniil.bazhenov/32/62_2.png) [@daniil.bazhenov](https://forums.percona.com/u/daniil.bazhenov)\
**Post date:** [January 9, 2026, 2:02pm UTC](https://forums.percona.com/t/open-source-postgresql-and-risk-mitigation-in-an-era-of-percona-community/40019/1 "2026-01-09T14:02:49Z")

</div>

As the year comes to a close and many of us start slowing down before the winter holidays, I find myself reflecting on patterns I’ve seen repeat, both as a customer and as someone working closely with the PostgreSQL ecosystem.

* * *
This is a companion discussion topic for the original entry at [https://percona.community/blog/2025/12/19/open-source-postgresql-and-risk-mitigation-in-an-era-of-acquisitions](https://percona.community/blog/2025/12/19/open-source-postgresql-and-risk-mitigation-in-an-era-of-acquisitions)