About PostgreSQL Core Team

Hi hackers:
I came across a blog that I was very impressed with, especially the views mentioned in it about PostgreSQL Core Team,Especially tom_lane in PostgreSQL Core Team,The new features submitted by some developers are often tainted with personal preferences, but fortunately not some new features do not lose the opportunity to be merged because of their personal preferences, This is blog url:https://www.percona.com/blog/why-postgresql-needs-transparent-database-encryption-tde/
[https://www.percona.com/blog/wp-content/uploads/2023/01/PostgreSQL-Needs-Transparent-Database-Encryption.jpg]<https://www.percona.com/blog/why-postgresql-needs-transparent-database-encryption-tde/>
Why PostgreSQL Needs Transparent Database Encryption (TDE)<https://www.percona.com/blog/why-postgresql-needs-transparent-database-encryption-tde/>
As Ibrar Ahmed noted in his blog post on Transparent Database Encryption (TDE). PostgreSQL is a surprising outlier when it comes to offering Transparent Database Encryption. Instead, it seems PostgreSQL Developers are of the opinion that encryption is a storage-level problem and is better solved on the filesystem or block device level.
www.percona.com

```

While I believe Transparent Database Encryption in PostgreSQL is important, I think it is just an illustration of a bigger question. Is technical governance in PostgreSQL designed to maximize its success in the future, or is it more about sticking to the approaches that helped PostgreSQL reach current success levels? For a project of such scale and influence, there seems to be surprisingly little user impact on PostgreSQL Governance. The PostgreSQL Core Team<https://www.postgresql.org/developer/core/> consists of “seven long-time community members with various specializations” rather than having clear electable positions, as many other open source organizations do. The development process in PostgreSQL is based around a mailing list<https://www.postgresql.org/list/pgsql-hackers/> rather than more modern and organized issue tracking and pull-request-based development workflows. Interested in PostgreSQL Bugs<https://www.postgresql.org/docs/current/bug-reporting.html>? There is no bugs database that allows you to easily see which bug is confirmed and what version it was fixed in a user-friendly way. Instead, you need to dig through the bugs mailing list.

```

[cid:02faaf41-94ca-4bda-a940-dd8192724467]